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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

5964.0. "Translate/Load MIB on an alternate node???" by KAOFS::CARSWELL () Tue Apr 26 1994 10:25

	
	I would like to know the risks of the following scenario, and/or
if it is even possible.

	We have MCC 1.3 running on a 2-node VMS V5.5-2, VAX 4000-400 cluster, 
which is in production and provides the management framework for a VERY large 
customer. This system CANNOT go down, and consequently is on UPS, and DEISEL
generator, and even has an exact duplicate clone  'idling' in another
DEC facility approximately 30 minutes away.   The Clone is also connected
to the customer's network, but is booted under different system roots, with
different node names. (When/if the main cluster goes down, we reboot the clone
into the primary roots, and voila, we're back on the air.)

	The primary production nodenames are HHLFM1 and HHLFM2, and when
idling, the clone is recognized as HHLFM4 and HHLFM5. (We have to keep the
clone online so we can copy production logs and datafiles to the appropriate
directories, therby ensuring the viability and usefulness of the clone.)


	Ok so here's my question, (Finally, you  say!)

	I want/need to use the CHIPCOM MIB, but I really don't want to shut MCC 
down for 6 hours in order to translate and load the new MIB.
(I did this on the clone, and it took that long using MCC_TCPIP_MTU.COM, and
and there were no users on the system at the time.) 
Can I copy the dictionary(and any other pertinent files{?}) over to the clone, 
execute the MCC_TCPIP_MTU.COM, and then copy back the updated dictionary, etc.
I realize that MCC would have to be restarted on the production node in order 
to read/utize the updated dictionary, but it wouldn't have to be totally down
for 6 hours.

1) Is this feasible??? 
2) Would the different node names on the CLONE cause problems? 
   (since it is running as HHLFM4/5) 
3) Am I overlooking something else?

	ANY comments would be appreciated.


	Regards,
		Gord C.
T.RTitleUserPersonal
Name
DateLines
5964.1Please search the conference before reposting questions.SCCA::daveAhh, but fortunately, I have the key to escape reality.Tue Apr 26 1994 11:2914
This exact topic has been discussed many, many times.

Simply:

	Copy the dictionary to a working directory,
	Define the MCC_* Logicals to point there for
		this one process only.
	Update the dictionary.
	Copy the dictionary files (MCC_FD*.* (not .LOG))
		back to the original MCC_SYSTEM:
	Restart MCC with the new dictionary.

The only "down time" is the time it takes to restart MCC.