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

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

1425.0. "Hubwatch v3.0 not discoving DB90" by GIDDAY::CHONG (Andrew Chong - Sydney CSC ) Thu Sep 15 1994 05:18


	A large customer has many DH90's, each hub has a DB90 in slot 8.
He also has many DA90's which is in slot 7.
	After upgrading to Hubwatch V3.0 , DA90's to V2.1-03, DB90's to
V3.1 , he finds that where a hub has a DA90 and a DB90, in 80% of these hubs,
Hubwatch does not show the DB90 in the hub. He can't add the DB90 into 
the hub either. Hubwatch has no problem discoving DB90 where the hub does
not have a DA90.

	Any idea what may cause this problem ? This problem was not with
V2 of Hubwatch. 

Andrew
T.RTitleUserPersonal
Name		DateLines
1425.1I don't think it is a HUBwatch problemROGER::GAUDETBecause the Earth is 2/3 waterThu Sep 15 1994 13:2012
Andrew...

   Any chance you can get a console connected to one (or all) of the DECagents
to view the community configuration (menu option 13)?  Also, what version of the
DECagent did they have before the upgrade?  If it was prior to V2.0 I am
concerned that perhaps the database conversion did not work as it was supposed
to.  If it was V2.0, then I am at a loss to explain the problem.  I am also
concerned about why you cannot add the bridges manually through HUBwatch. 
Knowing what the DECagent "thinks" is in the hub might help us figure out what
the DECagent is telling HUBwatch.

...Roger...
1425.2Reset of DA90... May bePADNOM::PEYRACHEJean-Yves Peyrache Country Support Group FranceThu Sep 15 1994 13:5314
    
      >> After upgrading DA90 to V2.1-03
       from which version ??? V1.0 V1.1
    
      Have you tried to reset the DA90 with Factory current/factory
     setting?
    
       I have already seen these strange problem during upgrade from older
       version of Da90, reset the DA90 cured the problem.
    
        hopes thats help you
    
         Jean-Yves
1425.3extra community was created !GIDDAY::CHONGAndrew Chong - Sydney CSC Fri Sep 16 1994 01:5416
	
	Thank Roger and Jean-yves for your suggestions.

	The DECagent was at V1.1 before the upgrade. 

	It turns out that in each case where the agent could not see the bridge,
there is an extra community in the community table. For example if the DECagent 
manage 2 other hubs, there would be a third community called public-3 where the
missing bridge is found (this would explain why it cannot be added to the hub
where the agent is). Deleting the community and enabling polling has put the
bridge back to its proper hub. 

	I am curious as to how the extra community got created on its own.

Regards,
Andrew
1425.4V1.1 had the power of creation!ROGER::GAUDETBecause the Earth is 2/3 waterFri Sep 16 1994 13:349
Prior to V2.0 of the DECagent code, there was a "feature" of the DECagent's
auto-discovery/poller code which caused it to create additional communities when
contact with a DECbridge was momentarily lost.  The code was supposed to "merge"
the communities back together when contact was re-established, but there was a
bug (or two) which caused this not to happen under some circumstances.

What you have done to solve the problem is exactly the right thing to do.

...Roger...