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

Conference ranger::pathworks_netware

Title:PATHWORKS for OpenVMS (NetWare) Conf.
Notice:Shipping on OpenVMS/Alpha and OSF/1 - ECOs=314.* - Kits=21.*
Moderator:DELNI::GORCZYCA
Created:Wed Nov 04 1992
Last Modified:Tue Jun 03 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:805
Total number of notes:2930

792.0. "How to change a NetWare Cluster Volume flag" by ALFSS2::MCKINNEY_D () Mon Mar 17 1997 18:50

    Hello All.
    
    My name is Donnell mckinney. I am with the PATHWORKS Support Group.
    This is my question. Can the "Cluster Volume Flag"  Active be
    changed? If so how. If not why not?
    
    $SCONSOLE
     2. Configuration Menu
     3. Services Configuration Menu
     1. File Services Configuration Menu
     3. Edit a Volume
    
    
    1 (C) SYS     _$1$DIA5:[PWVN$SYSVOL]
    
    Press RETURN FOR MORE, or enter volume number and press RETURN: 1
    
    Volume Name		SYS
    Directory		_$1$DIA5:[PWVN$SYSVOL]
      .
      .
      .
    Cluster Volume Flag	  ACTIVE
    
    If I try to downarrow to this field the screen cursor skips over it.
    However, I can toggle the 'ACTIVE' field on non-system volumes.
    How can this value be changed. The customer's configuration is in
    a cluster envirnoment.
    
    Thanks to all.	 
T.RTitleUserPersonal
Name
DateLines
792.1Does this help clarify it?CPEEDY::COOKJust say NO to that AccViO! - Java!!!Thu Mar 20 1997 15:5238
    
    Conceptually, here's how it's *supposed* to work:
    
    If you are in a clustered environment, you can be running more
    than one NetWare server in the cluster.  Thus, volumes can be
    initially specified as either:
    	(1) Cluster-wide (will be mounted by each/every NetWare server
    		that starts in that cluster)
    
    				or
    
    	(2) Node-specific (will be mounted only by this server)
    
    
    Having said that, I have not [yet] attempted to reproduce the
    problem you seem to be having, partly because I'm not exactly
    sure how your volume was initially specified.
    
    But, I'm quite certain that you can work around whatever problem
    you're seeing by using SCONSOLE to:
    	(1) Remove/delete the volume (that operation won't alter the
    		contents of the files in that VMS directory tree)
    	(2) Add that same volume back into the system, making sure
    		that you specify which behavior you want.  Make sure
    		that you use the same name as before for the volume
    		and that you specify the same VMS-directory as was
    		specified as before.
    
    Don't forget that you need to bounce the server (stop/restart the
    server) after doing those 2 steps, to make the changes visible to
    the users.
    
    Does this help?
    
    						Dave