Conference netcad::hub_mgnt

832.0. "Add Module problems...." by WARNUT::BANKST (Network Mercenary) Thu Mar 17 1994 07:51

    I am still having problems adding modules into a HUB, and its driving
    me nuts!
    
    I have an Agent 1.0 in an 8 port hub manageing another hub via a bridge
    90 V3.0 s/w.  I have the agent defined in the agent table in HUBwatch
    OK, and I have the the hub added in the community table for the agent,
    no problem, and I can see the autodiscovered modules in this hub OK,
    and manage them, so I can do most things. I also succesfully added a
    90L+ that wasn't autodiscovered, and can manage that OK.
    
    Now, I have two brouter 90 and a DS90TL in this hub.  The brouters
    appear as unknown modules, which I can't delete, and the 90TL doesn't
    appear at all.
    
    I have IP and SNMP community strings configured on the brouters and 90TL,
    and have entries for them in the agents table, and I can manage them as
    standalone modules OK.  They all have different community names, as the
    docs say they must be or the second device with that name will have the
    name ignored.
    
    So, from here I make the hub these modules live-in the current
    community, and get a HUB display up.  I select the slot the module
    lives-in, say the 90TL as this slot is empty, do CTRL/A and fill in the
    panel that comes up with module type, mac address, ip address the
    modules SNMP community name (not the agent or its community name) and
    hit the apply button, and get an unable to add module message.  The
    same goes for the brouters, and also I can't delete the 'unknown'
    modules from their slot, the 'apply' button is greyed out.
    
    So what am I doing wrong?  
    
    Is there a tie-up somewhere in the community names between the DECagent
    90, the communities associated with the agent and their community
    names, and the modules in the hub with their own SNMP agent such as the
    90TL and brouters?
    
    Also in the case of the 90TL, does the server name as configured in the
    server have to match the name I give the server in the agent table?  
    
    Perhaps someone can step me through the procedure to add a module,  the
    grey areas for me are the tie-ups between SNMP community names used for
    the agents, the agent communities, and the SNMP agents in modules in
    the hubs.  
    
    I have read the documentation a number of times and just can't see
    whats wrong.
    
    HUbwatch is T2.8 BTW
    
    	The help is very much appreciated
    
    					Tim
    
    PS I wish I had some kit in the office, I have to 'practice' on site
    which is not goodness.....

    > I have an Agent 1.0 
    
    Do you really still have DENMA V1.0 firmware.   If so you need to
    upgrade to V2.0.  V1.0 is very old.  It's not surprising that lots
    of things don't work with it.
    
    Regards,
       
    Bob

	You need at least DECagent V1.1 to recognize the DECbrouters and 
	DECserver 90TL.

	At this point, you might as well upgrade to V2.0, rather than V1.1

As Jack said, you might as well upgrade the DECagent to V2.0.  Besides,
HUBwatch/DOS V2.0 (now available) requires DECagent V2.0.

...Roger...

I have the kit and docs in my bag, so off I go......

	Thanks chaps

		Tim