Conference azur::mcc

    did you check the release notes and installation guide?
    
    (Release notes have things like, make sure your TDF is a negative
    number...)
    
    What do you want to "make sure" about?
    

    
    Yes I have read and followed the release notes and installation guides.
    My TDF is negative and correct for EST.
    
    I am trying to "Register" a NODE4 but get back the same error as is
    first listed in note 282. MCC-Service error.....
    
    I thought it was something I had not done. So what I am looking for is
    after the install is done and assuming DNS is set up. What next..start
    to register nodes???? Or is there something else first?
    
    

    There is no formal written document so far. (may one in future !!)
    
    First thing to check is whether all the required DNS directories are
    created. The set of such directories are documented in the release
    notes.
    
    Second thing is to make sure you start with a clean name space. ALL 
    the entities that have been registered prior to MCS kit need to
    deregistered BEFORE  you install MCS kit. If you have already installed
    the MCS kit, you can clean up the name space using DNS$CONTROL.
    
    If the problem persists, let us talk...
    
    / Jesuraj

Hi Bill,

	This is Thien Doan,  I would like to find out what version of MCC you
	have installed so that I can point you to some doc that will help to
	start.

	I have the latest version of the IFT T1.0.1 installed and running fine.
	A few question,

	Are you creating you private name space ?

	Depend on the version of the kit, you may have to install other versions
	prior to the latest kit.

	Did you start out with the User's Guide. It will help you alot in getting
	use to the MCC syntax and features.

	Please let me know if I can be any help.


Have fun.
Thien Doan
EIS/NMS

All the replies to this notes seem to be searching for a problem that does 
not yet exist.  The problem is not determining what when wrong, but what to
do after installing the software.  In otherwords, now that it passed the 
IVP and I set up the namespace ... now what happens.   A partial answer
exists in the Phase IV AM guide.  There needs to be an amendment to the 
Use guide or what ever that gives the use a general hint about which of 
the 80000million commands will lead to management heaven and in what order
things should be done.  Maybe even a check list.... like

1) setup an configure DNS and it's access control
2) inventory your network for node, bridges, routers names and addresses, etc.
3) register all your nodes, etc. using the mumblyfoo.com file
   assign reference information
3) create alarms and associated procedures and batch files, see the 
   mumblyfoo_alarms files
4) create domains and populate them to reflect areas of responsibility 
   create a heirarchy from the backbone down
5) distribute namespace directory replicas

The goal is to set MCC up in such a fashion to make the network monitor
and correct itself.  What do YOU want MCC to do for you, why are you
using MCC?   /Claudia

    
    RE: 290.5: good idea, I will send along your suggestion to the writer
    for the DECmcc Use manual.
    
    thanks
    

    What's the IDP for DEC ?    (We will be using the Corporate namespace)
    I need to know what to type in in response to this question asked by
    the installation procedure.
    
    Thanks 
    
    Lou Falek

You may wish to consult with the EASYnet folks and discuss with them 
how you plan to use the Corporate namespace, in advance of your attempt
to use the corporate namespace.  A mail message that I received many months
ago listed the planned EASYnet IDP's based on X.121 (X.25 circuits), but
it would best to get the latest information from the EASYnet folks.

regards,

\steve


                <<< Note 290.7 by RUMOR::FALEK "ex-TU58 King" >>>
                     -< Do we have one network-wide IDP ? >-

    What's the IDP for DEC ?    (We will be using the Corporate namespace)
    I need to know what to type in in response to this question asked by
    the installation procedure.
    
    Thanks 
    
    Lou Falek

    And please post your findings here. I seem to remember askingthis same
    question about 2 months ago... I'm sure someone else will want to
    know...

/doug

From:	58003::HUTCHINSON "Sam H - ISNS Data Networks 273-5154  01-Oct-1990 0742"  1-OCT-1990 09:43:03.29
To:	IAMOK::KOJM
CC:	RUMOR::FALEK,HUTCHINSON
Subj:	RE: MCC use in the Namespace (I forwarded this to Jane too.) Can you answer Lou's question? Post an answer too?

Today's answer is "49". we are using the default IDP for transition. We have
additional IDP's scheduled for use (see SHIRE::ET$DATA$DOC:W3.PS for list of
documents, one is the IDP recommendation for transition); there will be an
IDP per routing domain. Someday down the line we might move back to a single
global IDP (with a different format, but that's away's off).

Regards, Sam