Conference turris::microvax

MicroVAX 3100-98/88 and VAX4000-108 System Release Notes

Here are minor restrictions with the systems.


1. Internal SCSI cable on MV3100-98 and -88
   -Some of the earlier systems shipped with an internal SCSI cable
    that could not connect all six drives in a worst-case 
    configuration.

   ANS: If this is an issue, use the 17-04441-01 Rev B SCSI cable. 
        It is recommended that the longest SCSI removable device 
        be in the bottom slot.

2. Power supply connectors
   -Some of the earlier systems shipped with five 4-pin SCSI power 
    connectors instead of six.
   
   ANS: If this is an issue, add a 17-01389-01 power splitter cable 
        to the system.

3. Console shows the DSW43 as a DSW41/42.

   ANS: There are no plans to change the console to reflect the 
        DSW43 part number.

4. TZK11 in the top slot will hit the CPU chip.

   ANS: Mount the TZK11 in either of the bottom two slots. It is 
        recommended that the longest SCSI removable device be in 
        the bottom slot.

5. OpenVMS VAX versions 5.5-2, 6.1, 6.2, 7.0 and 7.1 do not properly 
   specify the correct system variant. Systems will work properly 
   but during a SHOW CPU or while running UETP, the systems are 
   identified as follows:

              System            Shown as
              MV3100-98         MV3100-95
              MV3100-88         MV3100-90
              VAX4000-108       VAX4000-105A

    ANS: Support for Catamount will appear in the following
         Remedial Releases:

              Version           TIMA Kit #
              V7.1              V71R05
              V7.0              V70R28
              V6.2              V62R59
              V6.1              no remedial kit being created
              V5.5-2H4          in process

6. QBUS connectors may be upside down.
   -Some of the earlier VAX4000-108's may have shipped with the QBUS
    connectors mounted the wrong way. The proper direction for the 
    QBUS cables should be towards the bottom of the box for proper 
    cable management.

    ANS: If the QBUS cables mount the wrong way, remount the cabinet 
         connectors in the proper direction.

7. External cables on the SCSI ports.
   -Some of the combination differential/single-ended 50 pin HD
    to 68 pin HD SCSI cables will cause a problem with the system.

   ANS: If connecting a device like a BA364-A* or a wide tape drive to
        the SCSI bus, use the BN31V-01 50 pin HD to 68 pin HD cable.

    Hi,
    
    My customer implemented what must of been one of the first of the 3100
    Model 98 systems late last calendar year.
    
    It's running advanced process control in a refinery environment and
    replaced a 4000 Model 90A.  The upgrade was driven by memory
    requirements that exceeded 128MB. 
    
    The customer is extremely pleased with this system except for one area. 
    This system is one of 5 VAxes and 6 Alphas that use FDDI as a cluster
    interconnect.  These systems basically run the refinery.  The new 3100 is 
    clustered with the rest of the nodes via ethernet and unforunately is 
    causing problems on cluster startup.  Further complicating matters is due 
    to the criticality of these systems all data is shadowed across
    seperate nodes.   Unfortunately, some of the applications this system runs 
    are only available  on VAX so an Alpha is out of the question.
    
    The customer and our local MCS rep believe there are PCI slots in these 
    systems. Is this correct? and if so are there any plans to support a
    PCI  FDDI adapter or any FDDI adapter for that matter?
    refinery.
    
    These really are remarkable systems, and given their performance and
    scalability, a high performance network interconnect makes sense.
    
    Bill

    if you need FDDI, you can attach the B400X off of the 4000-108 and use
    the DEFQA Qbus to FDDI module. That's the only FDDI port we have.
    
    jim
    

    Thanks for the quick reply!
    
    Is there a way to "upgrade" the 3100 to the 4100?
    
    The unfortunate part about the DEFQA is the Q-BUS limits the effective
    FDDI throughput to 16Mbits.
    
    Bill

    If this system follows the other upper-end MicroVAX 3100 series, it
    uses a similar processor module as the lower-end VAX 4000-1xx series,
    but different I/O widgets and box.  It's a box-swap for an upgrade.
    And the 3100 series traditionally lacks a general-purpose I/O bus.

    I'd look at a PCI-based Alpha system for faster FDDI I/O...

    In this case, it's the same box and cpu module, although set up
    differently. You'll have to add qbus cables, HSD10,...... to the
    system.
    
    I've asked Ed Yee the product manager to respond to this one.
    
    jim

        If it is possible to convert MicroVAX 3100-98 to a VAX 4000-108,
        I'd really appreciate quick information about "how to".
        
        For my specific need (wrong order made and very tight schedule)
        I'd really need DSSI capability on the ordered 3100-98. I.e. if
        I add KFDDA to the system plus DSSI cabling, use the internal RZ
        disk as a SCSI disk (no time to add internal HSD10, no need for
        QBUS), what would the magic command to force the CPU board to
        identify itself as VAX 4000-108?
        
        This way we would be able to avoid shipping two VAX 4000-100A to
        customer because of this bloody mistake.
        
        _veli

        And further, can I use the same KFDDA that is on a VAX
        4000-100A? I have one spare part and could probably get another.
        
        _veli

    Nope, different KFDDA all together....

    The command to switch CPU type in FEPROM is
      T 9D 57 to make CPU think it is a KA57 (VAX 4000-108)
      T 9D 59 to make CPU think it is a KA59 (MV 3100-98)
    
    	Harold C.
    

From:	MSBCS::SPRATT "Bill, 223-0362, PKO3-1/N85, pole 23K  13-Apr-1997 1726 -0400" 13-APR-1997 17:42:53.36
To:	BOBR
CC:	JIME,CATHYP,SPRATT
Subj:	I: Blitz - Firmware Update for Vax 4000-108

From:	PROXY::SHORTIS      "TOM 223-2412, "Practice kindness, everyday!"" 10-APR-1997 08:08:56.95
To:	BILL
CC:	
Subj:	Blitz

From:	GIAMEM::TIMA_MGR      9-APR-1997 16:18:23.05
To:	PROXY::SHORTIS
CC:	
Subj:	GRAM: [TD 2269] Firmware Update for Vax 4000-108 - BLITZ

Author                    : MARCI R POTTER
User type                 : DBA 
Location                  : USTIMA
Vaxmail address           : CSC32::POTTER       

Copyright (c) Digital Equipment Corporation 1997. All rights reserved.

+---------------------------+TM
|    |   |   |   |   |   |   |
|  d | i | g | i | t | a | l |           TIME   DEPENDENT   BLITZ
|    |   |   |   |   |   |   |
+---------------------------+


   BLITZ TITLE: Firmware Update for Vax 4000-108

  

   PRIORITY LEVEL: 

   DATE:March 26,1997
   TD #: 2269

   AUTHOR:Heather Kane
   DTN:223-4712
   EMAIL:[email protected]
   DEPARTMENT:RSE

   =================================================================

   PRODUCT NAMES:Vax 4000 108

   PRODUCT FAMILY: 

   Storage         ___
   Systems/OS      _X_
   Networks        ___
   PC/Peripherals  ___   
   Software Apps.  ___


   BLITZ TYPE: 

   Maintenance Tip           TIMA::INFO_X_  
   Service Action Requested  ___  


   IF SERVICE ACTION IS REQUESTED: (Check all that apply.)

   Labor Support Required     _X_  
   Material Support Required  ___  


   Estimated time to complete activity (in hours):
   Will this require a change in the field's inventory:  Yes __X_  No ___
   Will an FCO be associated with this advisory?  Yes ___  No _X_


   DESCRIPTION OF SERVICE ACTIVITY REQUESTED (if applicable):

	Firmware needs to be updated from V1.0 to V2.0 on VAX 4000-108

    *******************************************************************  


   PROBLEM STATEMENT:  

	When trying to install VAX 4000-108's in a DSSI cluster with other
	Vax4000-108's or any other clusterable sytem the cluster may not 
	configure properly and may cause hangs when a second system is booted.  

   SYMPTOM:  

	No matter what DSSI ID is set at console, when OVMS boots the ID is 
	always 7 so there is a conflict. 
     
   SOLUTION:	

	This is caused by OVMS not using the ID configured by the console with
	the SET_DSSI ID command. This is caused by a legacy code issue, 
	whereby OVMS will only use the DSSI ID value if Console firmware 
	Version is above 2.X.	    		

	The firmware needs to be updated to V2.0.  The version is available 
	by copying from :

  	may21::WRK:[MOPLOAD]kacat_v20_1.sys

   UPDATING PROCESS:

	The new firmware file needs to be copied to a mop$load area and then 
	perform the update.  Most systems have the firmware enable jumper
	(W3) on the CPU modules installed, which allows Firmware updates.  If 
	there is any problem with updating refer to the Vax4000-108 On-line 
	Service Guide as a reference.
 
***** On Server System *****

$ MCR NCP

NCP>SET CIRCUIT ISA-0 STATE OFF
NCP>SET CIRCUIT ISA-0 SERVICE ENABLED
NCP>SET CIRCUIT ISA-0 STATE ON
NCP>EXIT

$
$ COPY kacat_v20_1.sys MOM$LOAD:*.*
$
***** On Client System *****
>>>b/100 eza0

 (BOOT/R5:100 EZA0)

  2..

Bootfile: kacat_v20_1

-EZA0

 1..0..

FEPROM update program
                        ---CAUTION---
--- Executing this program will change your current FEPROM ---

Do you want to continue [Y/N] ? : y

Blasting in V2.0-1.   The program will take at most several minutes.

DO NOT ATTEMPT TO INTERRUPT PROGRAM EXECUTION

Doing so may result in loss of operable state !!!
+----------------------------------------+

10...9...8...7...6...5...4...3...2...1...0

FEPROM Programming successful
?06 HLT INST
        PC = 00008E24

>>>

cycle power


   VERIFICATION:

	Set DSSI ID on multi-node cluster as required and verify there are
	no conflicts.


   LARS INFORMATION: (Supplied by MCS)

       Attention Service Personnel: Begin the comment field of your LARS
       with the word "BLITZ" when you perform an activity associated with a
       BLITZ Type "Service Action Requested".



                     *** DIGITAL INTERNAL USE ONLY ***

\\ GRP=TIME_DEPENDENT CAT=HARDWARE DB=CSSE_TIME_CRITICAL
\\ TYPE=KNOWN_PROBLEM TYPE=BLITZ STATUS=CURRENT PROD=DEC4000-XXX PROD=4XXX