Conference azur::mcc

The TransLAN AM makes use of the Ethernet Access Common Routines
(mcc_ea_*) to communicate with the Bridge, just like the Bridge AM.

There is a known problem with the RBMS point product that prevents use
of the Bridge Protocol Type by these Routines as long as the RBMS's
BML detached process is active.

Is RBMS running on this sytem?

					Chris

 

what Chris said.

Also note that you can get an error similar to that if someone is using the REC
screen on a bridge while you're trying to manage it from the AM.
/doug

    
    Hi,
    
    There are 3 LTM process windows active
    A VMS process od - NMS_RBMS$BMLPRC
    No REC screens active
    
    Sounds like .1 to me. Clearing out other RBMS jobs and will try again.
    More later & Large Thanks,
    Jeff.
    
    

    Hi,
    
    Well,
    
    Tried to clear other RBMS processes via NMS_RBMS$shutdown.com which ran
    without error. Then tried to register the TLB III via IMPM. IMPM sat
    there for up to 20 minutes. I figured that I blew away the TLB AM use
    of RBMS.
    Restarting with NMS_RBMS$startup.com produced the 'protocol in use'
    error when again we registered the TLB III.
    I stopped LTM(s), and other SMS components during this test.
    
    Is there something else that I should look for?
    Confused,
    Jeff.
    p.s.
    Is it possible for a remote TLB console port  user to bring up a REC
    screen on my end's TLB? I've verified that my end has no tube on it
    that could have created a REC screen & activated RBMS in the TLB. Just
    checking.
    
    Note also that the SMS components are installed now. I installed BMS
    only on my previous 3100 and registered this same TLB III with no
    problem.
    

>    Tried to clear other RBMS processes via NMS_RBMS$shutdown.com which ran
>    without error. Then tried to register the TLB III via IMPM. IMPM sat
>    there for up to 20 minutes. I figured that I blew away the TLB AM use
>    of RBMS.
>    Restarting with NMS_RBMS$startup.com produced the 'protocol in use'
>    error when again we registered the TLB III.
>    I stopped LTM(s), and other SMS components during this test.
 
 Note really sure what you're trying to say, but:

  1. DECmcc TLB AM does NOT use the RBMS detached process.
     Running nms_rbms$shutdown.com is correct (or $stop/id=xxx>.
     Please verify process actually got nuked...

  2. Not sure why IMPM "sat there for up to 20 minutes". Can you
     try REGISTER using the FCL PM (IMPM Register also adds the
      entity to a Domain)?

  3. RBMS is the only thing (that I'm aware of) on the DECmcc SMS package
     that will interact with DECmcc TransLAN AM.

>    Restarting with NMS_RBMS$startup.com produced the 'protocol in use'
>    error when again we registered the TLB III.
>    I stopped LTM(s), and other SMS components during this test.

At this point I don't understand what you're trying to eliminate here.  It's
very clear to me that you simply can't run RBSM and the Translan AM
concurrently.   If you've got the Bridge AM and the most current DECmcc kit,
why on earth are you using RBMS anyway ?!?    There is *no* capability in RBMS
that has not been superseded by DECmcc-BMS V1.1 and the Bridge AM.

You will get 'protocol in use' errors when ELMS or RBMS (the product) try to
use the RBMS protocol concurrently with the Translan (or BRIDGE) AM.  Shut down
the one you're not using and it should work.   If it still doesn't work after
shutting them down, *then* you've got a problem.    

>    Is it possible for a remote TLB console port  user to bring up a REC
>    screen on my end's TLB? I've verified that my end has no tube on it
>    that could have created a REC screen & activated RBMS in the TLB. Just
>    checking.

Yes.  All someone has to do is connect to a terminal to a Translan console
anywhere in your network.  Then from that terminal he/she can do a virtual
terminal connect to anyother translan in the network and fire up a REC screen.

/doug

    
    With this data I'm now of the mind that the TLB AM is accurately
    reporting the results of the Register directive, as expected. (excuse 
    the confusion). I'll debug the rest of the environment next week.
    Thanks for the feedback.
    Jeff.
    

    
    For the record...
    
    Found RBMS startup proc invoked within Systartup_v5.com. Removed it,
    rebooted and registered TLBs without error. View of forest obscured by
    trees.
    
    Jeff.