[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

4814.0. "Bridge AM V1.3 BUG" by ZUR01::SCHNEIDERR () Mon Apr 05 1993 05:08

Hello,

If you want to look to the Protocol Database with the IMPM then you won't 
find one. You have to register the Prot Database manualy. With the FCL it works
fine.

This seems to be a bug close to that one with the Forwarding Database in V1.2



regards Roland

BTW: It tested it with "EMS 2.3" and "BMS 1.3 plus ELM 1.3"
T.RTitleUserPersonal
Name		DateLines
4814.1Will look into itQUIVER::HAROKOPUSTue Apr 06 1993 10:446
    Roland,
    
    I thought that this was fixed with the V1.3 bridge AM.  I'll
    take a look at it.
    
    -Bob
4814.2Can't re-produce... more info. pleaseQUIVER::HAROKOPUSWed Apr 07 1993 11:2514
    Roland,
    
    I was able to access the protocol database just fine from here.  I
    even added and deleted some entries with no problems.
    
    Can you describe in more detail the problem that you are having?  From
    the description in .0 it sound like you can't do anything until you 
    register the protocol database.  I have not seen that behavior here.
    
    Also, what model bridge are you using and what is the firmware version?
    
    Thanks,
    
    Bob
4814.3Does re-register help?MOLAR::MOLAR::BRIENENNetwork Management Applications!Wed Apr 07 1993 14:593
Was the problem bridge previously REGISTERed with V1.2 ?

Does REGISTERing the bridge from scratch with V1.3 fix the problem?
4814.4I think Chris has the answerQUIVER::HAROKOPUSWed Apr 07 1993 18:0718
    Chris may have the answer here.   V1.2 did not register the protocol
    database when the bridge was registered due to a bug in the
    Registration FM with variant fields.   
    
    The problem was that
    the LANbridge 100 and 150's do not have a protocol database, but the
    Registration FM would try to register one for these models anyway.
    This caused the registration of these bridge types to fail.
    
    The short term fix was to never register the protocol database and
    have the user register it from the IMPM before using it.
    
    The Registration FM bug has been fixed so now in V1.3 the protocol
    database is registered when the bridge is registered.  Therefore,
    I suggest re-registering bridges that were registered by V1.2 before
    trying to use the protocol database from the IMPM.
    
    -Bob
4814.5Your rightZUR01::SCHNEIDERRTue Apr 13 1993 11:2710
Hello,

Sorry for the long delay. You're right, if you start from scratch, than the Pro.
Database is registered properly. But if you upgrade, you have the old problem
with the not registered database.

So you have to dereg all your bridges and reregister them.


Thanks Roland
4814.6Upgrade to V1.3 - same problem!COMICS::WARDJWed Sep 08 1993 08:0023
    Hello,
    
    Can someone confirm to me that this is expected behaviour after
    upgradeing to ems V1.3.
    
    The customer upgraded to 1.3 and found that the protocol database had 
    dissapeared (amoung others) when he looked into a lanbridge 200.
    
    Deregistering and reregistering the bridge brought the database back
    ok.
    
    The customer claimed that he did not registered the protocol database
    manually on previous versions, is this a bug?
    
    If it is expected hehaviour is there an easy way to bring back the
    child entities for his bridges without having to de-register and
    re-register the bridge.
    
    Thanks in advance,
    
    Jon