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

Conference ssag::ask_ssag

Title:	Ask the Storage Architecture Group
Notice:	Check out our web page at http://www-starch.shr.dec.com
Moderator:	SSAG::TERZAN

Created:	Wed Oct 15 1986
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6756
Total number of notes:	25276

6464.0. "VAX4000 Model 108 SCA error" by QBUS::E_BURKHALTER () Mon Mar 10 1997 12:32

    
    
        I have an field engineer installing (2) VAX 4000 Model 108 systems
        in a dual host configuration.  Systems are running VMS 6.2.
    
        The DSSI interface is a KFDDA-AA.
    
        One system is node number 7 and the other is node 6 at
        the console level.  Both are node 7 if one system is booted
        and we $SHOW CLUSTER/CONT and add LPORT/RPORT.  The remote
        port is shown as node 7.
    
        If one system is booted then the other system is booted,
        they get the message " inappropriate sca control message".
        then we hang.
    
        If one system is at the >>> prompt and the other boots, 
        system operate fine.  If the reverse is true, the 2nd system 
        is fine.
    
        I ask the engineer to give me a sys layout and under show cluster/
        continous things lke RPORT, LPORT etc.
    
        FE hasn't called back with the info at this time.
    
        Has anyone seen this?
    
    Ed Burkhalter
    CSC Atlanta

T.R Title User Personal
Name Date Lines

6464.1 Confirm, Power-Cycle, IPMT XDELTA::HOFFMAN Steve, OpenVMS Engineering Tue Mar 11 1997 09:33 13

T.R	Title	User	Personal Name	Date	Lines
6464.1	Confirm, Power-Cycle, IPMT	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Tue Mar 11 1997 09:33`	13
	This sounds like an OpenVMS question, not a storage question. And if the console values for the controllers are set at unique DSSI addresses and OpenVMS is somehow switching all DSSI addresses to seven, that looks like a serious OpenVMS bug. (If it's just displaying the wrong address, that's still a bug.) I'll assume the customer or FE has set up the unique DSSI address values in the console, power-cycled the systems for good measure, and has then confirmed that the console addresses have not somehow mutated before OpenVMS has been bootstrapped. If so, i'd start with an IPMT.

   This sounds like an OpenVMS question, not a storage question.  And if
   the console values for the controllers are set at unique DSSI addresses
   and OpenVMS is somehow switching all DSSI addresses to seven, that looks
   like a serious OpenVMS bug.  (If it's just displaying the wrong address,
   that's still a bug.)

   I'll assume the customer or FE has set up the unique DSSI address values
   in the console, power-cycled the systems for good measure, and has then
   confirmed that the console addresses have not somehow mutated before
   OpenVMS has been bootstrapped.

   If so, i'd start with an IPMT.