Conference azur::mcc

    I was not able to reproduce the problem you describe.

    These are the steps to follow to Create a Static Entry in a Bridge's
    Forwarding Database as outlined on page 4-2 of the DECmcc Bridge Access
    Module Use Guide:

    	To add a static entry to the forwarding database, select the
    	bridge and forwarding database [from the map window], then open the
    	Toolbox.  Select Static Entry from the Toolbox and enter a physical
    	address.  [Click on OK to get the next dialogue box.]

    	Next, the Add Entity dialogue box is displayed.  Enter values for
    	the appropriate attribute, depending on the type of filtering you want. 
    	[In your case, click on the Disposition field and enter "Filter". 
    	Click on OK and you'll be instructed to move to the map window and
    	click on where you want the static entry put on your map.]  

    To Delete a Static Entry in a Bridge's Forwarding Database, bring down
    the Toolbox, and click on the circle with a single slash through it. 
    Then move the X pointer to the map and click on the static entry you
    want to remove.

    If you still can't get it to work, please post a reply here with the
    version and operating system you are using, version of DECmcc ELM you
    are running, the type of bridge you are using, and the exact steps you
    performed while in the Iconic Map.

    When I perform the sequence you describe, enter the address and click
    ok, I dont get the entity dialogue box, I get the operation -
    complete/plan box. When I ok this I then get the problems I described
    earlier. 
    
    The only way I can get the entity dialogue box is if I enter a
    completely fictitious address, but if I enter one which has already
    been learned in the forwarding db then I get the operation -
    complete/plan box.
    
    VMS Version is 5.4
    BMS 1.2, latest ELM
    
    Gary
    

| The only way I can get the entity dialogue box is if I enter a
| completely fictitious address, but if I enter one which has already
| been learned in the forwarding db then I get the operation -
| complete/plan box.

    I just tried it again, this time with a real address that the bridge
    has learned (one of its dynamic entries).  Using the Iconic Map, I
    created a static entry with an already learned address, showed all its
    attributes, and then deleted it.  All worked as described.

    Just out of curiosity are you using a local MIR or DNS as your
    namespace?

    mysterious!
    
    I am using local MIR
    
    Does the fact that I get the complete/plan window give any clue as to
    what's going wrong?
    
    Gary

| I am using local MIR

    Yes, that's what we have here, too.

| Does the fact that I get the complete/plan window give any clue as to
| what's going wrong?

    I *think* that window comes up when certain entities are not
    registered, but I'm not sure.  I can't find any references to a
    "complete/plan" window in my documentation.  Can someone from the IMPM
    group provide any clues to what's going on here?

    I'm baffled!

My customer has experienced exactly the same problem.
The problem is also reproducable on my workstation.

The problem is qared with number #3425


			Best Regards,


			Roland Fueglister (7)760-2498
			DS/Network Integration Center

    Based on the information given, it looks like the forwarding database
    did not get registered when the bridge was registered.  Try the
    following and let me know if it works:
    
    mcc>deregister bridge <bridge_name>
    mcc>register bridge <bridge_name> addr=<bridge addr>
    
    Then try to add a static entry to the forwarding database.
       
    Thanks,
    
    Bob

    Has anyone who having this problem tried the suggestion in .7 yet?   
    We have an outstanding QAR on this problem and we can't reproduce it 
    here so I need to know if we are on the right track.
    
    Thanks,
    
    Bob  

    When I raised the problem I was giving a training course and I don't
    have access to a system at the moment.
    
    However, during that week I did register a new forwarding db, double
    clicked on it and still got the same problem trying to register a static
    entry. I didn't deregister the old forwarding db though.
    
    Does this help?
    
    Gary

    any more info on this one?

    --> any more info on this one?

    We've been unable to reproduce your problem.

    Do you now have access to the system your were using where the problem
    occurred?  Can you try the work-around proposed in reply .7 and let us
    know if it works?

Based on the recommendation given in reply .7, I deregistered/registered a
LB200 with the IMPM as well as the FCL.
The assumption that the forwarding database is not registered is not true and
the problem described in QAR #3425 still applies.

Additionally I encountered a new message:
After the deregistration/registration of a LB200 I did the following with the
IMPM as well as the FCL:

DIRECTORY BRIDGE LB200_bridgename FORWARDING DATABASE

FCL  --> direcorty successful
IMPM --> directory successful + management window message:data type not
								supported


				Best Regards,

				Roland

    I still get this problem, and on Ultrix too, and on a VMS system built
    by someone else.
    
    Doing 
    
    MCC> CREATE BR name FOR DATA STAT ENT address DISP FILTER
    
    followed by adding static entry from the toolbox works ok (still the
    complete/plan box though, not the full one)
    
    Doing it all from the map behaves as follows:-
    
    Click on static entry in toolbox
    Enter address
    Get complete/plan box, ok that
    Static Entry entity is added ok
    Click on it, show char, get "Variant Information not found in Variant
    Selector list" (what the hell does that mean?)
    Try set char, window appears and immediately disappears
    
    Above behaviour occurs if entry has been learned as a dynamic entry,
    things work ok if address is fictitious.
    
    The fact that it also happens on Ultrix is suspicious - either I am
    doing something very obviously wrong or you are not recreating the
    problem properly.
    
    Any more help at hand? 
    
    Many thanks 
    
    Gary

    
    Thanks for the information.  I'll try it on T1.3.1 with the latest
    bridge AM to see if I can reproduce it.
    
    -Bob

    With the help of Jim Lemmon, this has finally been tracked down.
    
    This bug was exposed by the differences in the way that the IMPM
    and FCL handle the create operatation.   FCL attempts the
    create without checking to see if the entry is already a
    static entry in the forwarding database.   IMPM does a
    show bridge forw data static entry xxx to see if the entry
    is already there first.
    
    The problem is that for some addresses the bridge agent
    is returning a valid status even though the entry does not
    exist.  Therefore, IMPM skips the create operation and simply
    registers the entry.  Because the entry was never created any
    operation on it fails.
    
    I tried each bridge type and I was able to reproduce the problem
    on the LANbridge 200, DECbridge 5xx and 6xx.  I may be able to add
    some additional error checking to the bridge AM to work around
    this but it is ultimately a firmware issue.
    
    What I need to know is how severe an impact is this given that
    there is a workaround (just use FCL to create the entry).  Remember
    that if I don't defer this then this will hold up the shipment
    of DECmcc V1.3 as ELM is already holding up the V1.3 release.
    Given that information is it ok to address this at a later time either 
    in firmware of with a bridge AM workaround?
    
    Thanks,
    
    Bob
    
    

				Hi Bob,

I am glad to read that you are able to reproduce the problem.
Fortunately we can use the FCL workaround in the meantime.
I vote for deferring this bug.

				Best Regards,


				Roland

    Hi,
    I have just come across the same problem at a customer site.
    Anyidea when this will be fixed?
    I will try using the FCL for now...
    thanks,
    Miek

    any idea if this bug is fix ?
    					thanks Gianni