Conference azur::mcc

    
    
    I found it.  The Default Ethernet Type Filtering is hidden under the
    protocol database characteristics.
    
    Boy, what happened to the idea of consistency?
    
    Mike

| I found it.  The Default Ethernet Type Filtering is hidden under the
| protocol database characteristics.
|
| Boy, what happened to the idea of consistency?

    The ELM AM was designed around the bridge entity model, and not around
    what DECelms looked like.  Things like this are bound to happen, but I
    think it makes more sense to put Manual Mode and Default Ethernet Type
    Filtering with the Protocol Database child entity.

    If there are parts of the documentation that are unclear, please post
    what you don't like and perhaps we can make it better in the next
    release.

    Is a matter of fact, I looked all over help and wasn't able to find
    what I needed.  If I didn't spend the 2+ hours trying every possible
    sub entity class under Bridge, I would have never found it.  Also,
    what I found was the ability to perform Default Ethernet Type
    Filtering, Default SAP Type Filtering, and Default SNAP Type Filtering
    on the protocol database, but the Manual Mode still is not available.
    I am able to see the Manual Mode characteristic (-NOT RETURNED-) when
    I do a show bridge .bridge_name forwarding database characteristics,
    but this attribute is not settable, why?  Granted; I can effectively
    do the same thing as manual mode by setting the three default type
    protocol filters to true, but I should be able to set the forwarding
    database manaul mode attirbute..  Don't you agree???????
    
    NEI Network Management,
    Mike

I found it!

The command (according to OnLine Help) is:

	RESET BRIDGE id FORWARDING DATABASE Manual Mode = {True|False}

If I remember correctly, the side effects of entering Manual Mode argued
for mapping it as a RESET switch (at least at the time).

The Bridge Access Module Use Book (at least the Bookreader version that I
have) does document the switch in Section 4.12 "Resetting the Forwarding
Database". It might make sense to manage it in the text for Section 4
"Managing the Forwarding Database"...

Definitely confusing if you're a regular user of DECelms...

--------------
The help text:
--------------

ENTITY

  BRIDGE

    FORWARDING_DATABASE

      DIRECTIVES

        RESET

          Manual_Mode

              The Manual Mode argument, if set to True as part of the RESET
              directive, specifies that:

              1) Bridge address learning is to cease
              2) Multicase Entry child entities with
                 Management Created = False are to be deleted
              3) The bridge is to forward packets based solely on
                 Multicast Entries with Management Created = True
              4) The forwarding database attribute Manual Mode gets set to
                 True.

    I would like to know what those side effects were.  Talk about making
    a product so confusing that it scares customers to the competition.
    I tried the RESET command and then I looked via elms, it still did not
    change the MANUAL MODE to true.  What now?
    
    PS: Don't take me the wrong way.  I am not yelling at you.  You would
    	just expect a application so big to be a bit more consistant.
    
    Mike

    Manual Mode is listed in the Index of the DECmcc Bridge Access Module
    Use Guide.  In fact, its entry in the index says:

    	Manual Mode (qualifier of RESET directive for Bridge), 4-24

    This would have pointed you directly to the information you were
    looking for.  If the documentation is unclear, we would like to know
    how to fix it to make it better.  In this case I think it's been
    properly documented.

    If you don't have a Bridge Access Module Use Guide handy, please copy
    over the PostScript and print it out.  The bridge entity model in MCC
    is fairly complicated and I find I refer to the Use Guide very often.

    TNPUBS::USER$657:[PUBLIC.NMS.MAKO]DECMCC_ELM_BRIDGE_AM_USE_FINAL.PS is
    where it's located.

| I tried the RESET command and then I looked via elms, it still did not
| change the MANUAL MODE to true.  What now?

    It works for me:

$ mcc
DECmcc (V1.2.0)

MCC> show bridge defeb forw data manual mode

Bridge LOCAL_NS:.defeb Forwarding Database
AT 22-OCT-1992 10:55:34 Characteristics

                            Manual Mode = False
MCC> reset bridge defeb forw data manual mode true

Bridge LOCAL_NS:.defeb Forwarding Database
AT 22-OCT-1992 10:55:52

Entity successfully reset.
MCC> show bridge defeb forw data manual mode

Bridge LOCAL_NS:.defeb Forwarding Database
AT 22-OCT-1992 10:56:09 Characteristics

                            Manual Mode = True
MCC>

    Which bridge model are you using?

    
    Enough said.  I am still not sure why it isn't working for me, but at
    least I know it is something with the bridge.  I tried to set the
    manual mode via the point product ELMS v1.1 and it didn't work.  In
    fact, when I did a ELMS> SET BRIDGE bridge_name MANUAL MODE TRUE
    PASSWORD password, the command was excepted, but the Update switch
    changed instead.  It must be a hardware problem or a bug in the old
    bridge software that I have V2.1.
    
    Mike

    I tried this on a DECbridge 500 with software version 3.0 and it
    worked fine.   I recommend upgrading your bridge firmware to V3.0
    and seeing if that fixes the problem.
    
    Regards,
    
    Bob 

    
    I have tried in the past, but nobody wants to help.  Would you have a
    network pointer to the DECbridge software?
    
    Thanks,
    Mike

--> I have tried in the past, but nobody wants to help.

    It will be my pleasure to assist you in upgrading your bridge software. 

    I'll try to find you the loadable code on the network.  If I can't do
    that, I'll find out exactly what you need to do to get the latest
    version.

    /* Ed */

    The latest and greatest DECbridge 500 software is V3.0 and can be found
    on the network in the following location:

	LEVERS::USER$459:[VOYAGER_FW.FW_RELEASE.CUR_RELEASE]DEFEB030.SYS

    You can upgrade your bridge firmware using DECndu, the Network Device
    Utility.  Are you familiar with DECndu?