Conference azur::mcc

    Hi Ed,
    
    I'm not sure what is causing that error.  I looked it up and
    it's says it's a bad parameter in the QIO call so it could be
    almost anything.
    
    Here are a few things to look at though:
    
    1) Are there any other processes running on the system that have
    allocated the DEMNA?
    
    2) Are there any other processing running that use the MOP protocol
    such as the ELMS listener or TSM?
    
    3) Do you have the corect privs?  You need DETACH, LOG_IO and PHY_IO.
    
    4)  When you select choice 1 from the listener menu to assign the
    ethernet port what list of options is showing up?  What is the logical
    name of the DEMNA that you are using?
    
    
    Thanks,
    
    Bob
    
    

Bob, I found it.  If any other process has the device _EXA0 attached, it
won't run.  I got it running, but now it can't communicate with any of the
birdges.

Log of the STM Listener Spanning tree map is:

*** Spanning Tree Map FM (STM_FM) V1.3.0 Messages ***
(I)  Generating spanning tree map for domain LOCAL_NS:.bxb.
(I)  Automap parameters: Autoregister = TRUE, Reset = FALSE, Database = STM_LISTENER
(I)  Reading STM listener database...
(W)  Minimum time set for the Listener has not elapsed.
(I)  Polling for bridge identifiers...
(E)  Error polling bridge - bridge name: BR_08002B0F330B
- bridge address: 08-00-2B-0F-33-0B
(E)  Error polling bridge - bridge name: BR_08002B0F330C
- bridge address: 08-00-2B-0F-33-0C
(E)  Error polling bridge - bridge name: BR_08002B1C150B
- bridge address: 08-00-2B-1C-15-0B
(E)  Error polling bridge - bridge name: BR_08002B1C150C
- bridge address: 08-00-2B-1C-15-0C

Ad Nausium.  These are REAL bridges, which can be reached by ELMS and RBMS.  I
am having a similar problem with with the LTM_REPORTS product, which I beginning
to wonder if it's related to the DEMNA hardware.  Was this hardware around when
this piece of the application was developed???

Ed

    Hi Ed,
    
    I don't know of anything specific to the DEMNA that should cause
    a problem.   Could someone who works the MCC EA routines
    indicate if DEMNA presents any problems?     
    
    In the mean time please post the following:
    
    mcc>show mcc 0 bridge_am all status
    
    and 
    
    mcc>show bridge 08-00-2B-0F-33-0B all char
    mcc>show station 08-00-2B-0F-33-0B all char
    
    on a couple of the bridges in the list.
    
    Thanks,
    
    Bob
    

MCC> sho bridge 08-00-2b-0f-33-0b all char

Bridge {08-00-2B-0F-33-0B}
AT 26-MAR-1993 13:10:41 Characteristics

The requested operation cannot be completed
                      MCC Routine Error = %MCC-E-PROTOCOLINUSE,  protocol is in
                                          use and not available.
MCC>show station 08-00-2B-0F-33-0B all char

Station 08-00-2B-0F-33-0B
AT 26-MAR-1993 13:11:18 Characteristics

Examination of attributes shows:
                    Functions Supported = DEC_ENETV2
                    Maintenance Version = V3.0.0
                         Implementation = LANBridge 200/DEBAM
MCC>

Ed

re: .3

>> someone who works the MCC EA routines indicate if DEMNA
>> presents any problems? 

  I believe that would be Vinnie Guarino .. who was TFSO'd in December 8(

  I'm not sure who in DECmcc land has picked up the code.

  /keith

    I'll hazard a guess here.  I'm willing to bet, well maybe a nickel,
    that RBMS is running on the VAX where you are trying to access the
    bridge via the ELM-AM.  This was a problem before DECmcc when DECelms
    came out.  RBMS, used to 8038 protocol in an exclusive mode, and would
    not share it with any other application.  Do a show system and see if
    there is a process with an RBMS name imbeded in it.  If so, then RBMS
    can be shutdown with @sys$manager:NMS_RBMS$SHUTDOWN.
    
    Matter of fact, I think I talked to this customer when she call into
    the CSC, the ethernet address of the bridge looks very familier.  The
    system in question did have RBMS running on it.
    
    Steve Woestemeyer
    CSC/CS - Network Support Team

    I think Steve is correct.   There is a process running on this
    system (most likely RBMS) that has allocated the 80-38 protocol
    on the port in exclusive mode.  This is evident from the error
    message indicating that the protocol is already in use.   
    Shutting down this process will fix the problem.
    
    -Bob

Well, RBMS is running, but it wasn't me who called th CSC,  and I'm a he.

Ed


I'll give it a try.  tnks.