Conference netcad::hub_mgnt

    
    I have had similar problems and got it to work by adding a new
    community to the DA90 for the bridge in question and not using the
    standard public community. I cant remeber why this is, but it works
    here.
    
    Dave

    
    Hi,
    
    I've changed community name on DECagent 90 itself (with community name
    = decagent90), and after updating *.dat configuration file, the problem
    is still existing...
    
    16.188.48.120 hub900 "public" 5 2 AGENT900 # Agent Repeater
    16.188.48.123 da90 "decagent" 5 2 08-00-2b-bb-51-8d AGENT90 #
    16.188.48.122 ds900 "public" 5 2 08-00-2b-a2-a5-77 TERMSERV #DS900TM
    16.188.48.124 pb900 "public" 5 2 08-00-2b-a2-cb-4d RMON #
    16.188.48.123 da90 "decagent" 5 2 08-00-2b-25-94-57 BRIDGE #
    
    
    Any other idea ??
    Renato

    
    Renato,	
    
        1) Create a standalone community on the DECagent 90. Let's say
           call it bridge.
    
        2) Add the DECbridge 90 to this community (bridge).
    
        3) Add an entry to the HUBwatch Agent's File similiar to this:
    
           16.188.48.123 denma_bridge "bridge" 5 2 08-00-2b-25-94-57 AGENT90
               ^                         ^                ^
               |                         |                |
       IP addr of DECagent 90          cmmty         MAC of bridge
    
    Hope this helps,
    Bob 

    
    Bob,
    
    Hereunder the HUBWATCH configuration file...
    
    16.188.48.120 hub900 "public" 5 2 AGENT900 # Agent Repeater
    16.188.48.123 da90 "public" 5 2 08-00-2b-bb-51-8d BROUTER #
    16.188.48.122 ds900 "public" 5 2 08-00-2b-a2-a5-77 TERMSERV #DS900TM
    16.188.48.124 pb900 "public" 5 2 08-00-2b-a2-cb-4d RMON #
    16.188.48.123 db90 "bridge" 5 2 08-00-2b-25-94-57 OTHER #
    
    BUT, about your 1) suggestion, as I've any documentation about V2.1.3 
    DECagent software, I've just seen the (13) Show Community Option,
    where, by selecting "public" Community Index, I've got DECagent 90
    Slot Configuration... All is EMPTY, except slot 7 where DECagent is 
    inserted... HOW to apply your 1) suggestion, ie defining on DECagent90 
    "bridge" community related to DECbridge 90 ??
    
    Thank you for your help.
    Renato
    
    

    
    Bob,
    
    Please also note that the updating operation via HUBwatch of
    configuration file, returns sometimes erratic description (BROUTER ??
    OTHER ??... instead of my own selections, AGENT90 twice...)
    
    16.188.48.120 hub900 "public" 5 2 AGENT900 # Agent Repeater
    16.188.48.123 da90 "public" 5 2 08-00-2b-bb-51-8d AGENT90 #
    16.188.48.122 ds900 "public" 5 2 08-00-2b-a2-a5-77 TERMSERV #DS900TM
    16.188.48.124 pb900 "public" 5 2 08-00-2b-a2-cb-4d RMON #
    16.188.48.123 db90 "bridge" 5 2 08-00-2b-25-94-57 AGENT90 #
    
    

    
    Renato,
    
    	With V2 DECagent 90 you'll need to add the community via HUBwatch.
        In the Manage Table option of HUBwatch, select your DECagent 90's
        public community and then add a standalone community (ie db90) to
        it. Select this new community and then perform a [configuration]
        [add] operation on it, adding the DECbridge 90.
    
    Regards,
    Bob

    
    re:.5
    
    Renato,
    
    	We've seen this here as well. It is QARed.
    
    Regards,
    Bob

	Renato,
	I take here the opportunity to record our findings of yesterday, this 	
	will certainly be helpfull for other people 
	There is probabely different of possibilities to access a bridge 90 from
		a DEChub900. The one I will describe seems for me the best (and
it seems 		to work systematically which seems not always be the
case with Hubwatch 		;).

	1. Accessing the console of the agent 90 after an factory reset you see 
	 one default community.
		Using [13] from the menu
	Index 	Type	 	Community
	----- 	---- 		---------
	1	DEChub-8 	public
	
	2. Let us say that the IP address of the AGENT90 is 16.183.32.227
	   and the MAC address  08-00-2b-3e-ea-60
	   That the MAC address of the Bridge 90 is 08-00-2b-ba-88-9b

	3. You define in HUBWATCH$LIBRARY:HUBWATCH_AGENTS.DAT
		16.183.32.230 hub9h_ibm "public" 5 2 AGENT900 # IBM address
		16.183.32.227 hub9h_agt "public" 5 2 08-00-2b-3e-ea-60 AGENT90 
		16.183.32.227 hub9h_brg90 "public" 5 2 08-00-2b-ba-88-9b BRIDGE 
	 I know this sounds a little bit crazy to put an IP address for the 	
	 bridge but this works.

	 Remark that the IP address and the community of the AGENT90 is used for
			the bridge	
	
	4. You start Hubwatch with the IP address of the AGENT900
	
	5. Through Community -> Manage Table you make current the AGENT90

	6. You modify the HUB type in a HUB900 and then APPLY
	   You will see the display change from a 90 to a 900, see also [13]  	
	   using the console of the Agent 90
	  
	7. You click on the slot you want to insert your Bridge (The Agent90 	
	   does not recognize it automatically so you can put anywhere you want,
		   there is  no check :(
	   From the menu Configuration ->ADD
           the bridge using a name and the MAC address of the bridge
	
	8. So from now on you can click on the bridge and display information 	
	   from the AGENT90 in a hub900 view OR from the AGENT900 view, thats 	
	   great :))
		
	9. You remark that with this method no new community is used for the 	
	   AGENT90, verify that with [13] from the console.

	10. Also you will see some ISSUES :{{

		- From the AGENT900 a DECbridge 90 is always displayed as 
		   DECbridge90FL,  why tell me why ..

		- Because there is no check of the AGENT90 about the occupied 		
		  slot you can have a complete different view from the AGENT900 
		  and the AGENT90 if you have add your bridge in a wrong place 	
		  for instance.

		- Using the console of the AGENT90 function [13] you will see 		
		  your bridge recorded  with a status 'NO Reachable' 
		  tell me also why.

			

	I someone could have a look on 10, some improvement can be done there.
	
	Regards,
	Robert



	16.183.32.227 hub9h_brg90 "public" 5 2 08-00-2b-ba-88-9b BRIDGE 
	I now this sounds a little bit crazy to put an IP address for the bridge
t

>>	7. You click on the slot you want to insert your Bridge (The Agent90 
>>	   does not recognize it automatically so you can put anywhere you want,
>>		   there is  no check :(

The DECagent 90 will not discover modules in a DEChub 900 when the hub manager
has an IP address.  In this configuration the DECagent 90 is not allowed to be
the hub master, so the auto-discovery feature is disabled.

>>	10. Also you will see some ISSUES :{{
>>
>>		- From the AGENT900 a DECbridge 90 is always displayed as 
>>		   DECbridge90FL,  why tell me why ..

That is strange.  I do not know why.  Perhaps one of the MAM folks will take
this one?

>>		- Because there is no check of the AGENT90 about the occupied 		
>>		  slot you can have a complete different view from the AGENT900 
>>		  and the AGENT90 if you have add your bridge in a wrong place 	
>>		  for instance.
>>
>>		- Using the console of the AGENT90 function [13] you will see 		
>>		  your bridge recorded  with a status 'NO Reachable' 
>>		  tell me also why.

Right.  As stated above, if the DECagent is not the hub master, it relies on
manually entered configuration information and cannot correct for misplacement
of modules.  If you want the DECagent to manage the bridge, you will have to add
it to the DECagent's community using the HUBwatch Configuration -> Add window. 
It should then become reachable as viewed from the DECagent console.

Hope this helps.

...Roger...

    I've just spent *2* hours at a customer setting up an evaluation,
    trying to figure out how in the hell to make a DECbridge 90 managed
    from a DEChub900 with a DECagent 90 in it.  The documentation is
    totally useless on this subject.  It looks as though this note (prior
    entries) will solve the problem.....however.....
    
    A main feature of our hub strategy is the 'investment protection' and
    ability use 90 modules in the 900 as needed. The sheer effort to tweak
    the management stuff to work NEEDS TO BE CLEARLY AND QUICKLY DOCUMENTED
    AS SOON AS POSSIBLE!!
    
    I have several other customers who will run into this and hit a wall. 
    It won't be pretty when it splatters.  Can we document this quickly?
    
    Regards,
    j
    

    Table 3-8 on page 3-18 of the HUBwatch Install/Config guide documents
    the steps for doing exactly what you are trying to do.
    
    What did you find unclear about this table?  I will anticipate your
    feedback and pass it on to the documentation writer for this book.
    
    Thanks,
    
    Bob