[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

1624.0. "IP addresses of modules within a hub not being displayed" by CERN::JRS (John SHADE - 'Attila the Nun') Thu Oct 27 1994 11:17

I have a DEChub900 with a bridge in slot 3 and a concentrator in slot 6.
All three items have their own an IP address.

If I specify the address of the hub, HUBwatch (V3.1) displays the hub and the
two modules - but does not display the modules' IP addresses. If I specify the
address of the bridge, HUBwatch identifies it as a DEFBA and treats it as
standalone (picture of bridge in slot one of an otherwise empty hub). 

Any ideas why HUBwatch doesn't display the IP addresses of the modules within 
the hub (OBM terminal finds everything OK)?

An additional, perhaps irrelevant, piece of information is that another bridge
used to reside in slot 3 but is now standalone somewhere else in the network. 

Thanks,

-John
T.RTitleUserPersonal
Name		DateLines
1624.1Look at segmented display & also use console to verify this....NETCAD::BATTERSBYThu Oct 27 1994 12:078
    When you look at the HUB MAM segmented display, do you see
    the IP addresses for those modules? It should display the 
    in-band IP address of each. You could also verify whether both modules 
    really have IP addresses by re-directing to their respective slots from
    a terminal connected to the HUB console port as a sanity check of
    what you are seeing with HUBwatch.
    
    Bob
1624.2Both modules really do have IP addressesCERN::JRSJohn SHADE - 'Attila the Nun'Thu Oct 27 1994 12:218
>> You could also verify whether both modules really have IP addresses

That's what I meant by "OBM terminal finds everything OK". Sorry, I should
have been a little clearer. However, what is the "HUB MAM segmented display"?

Thanks,

-John
1624.3HUB LCD display....NETCAD::BATTERSBYThu Oct 27 1994 12:265
    At the top of the HUB, there is a 20 character 2-line LCD
    display that you can view which will sequence through each
    backplane slot showing whether modules are active etc.
    
    Bob
1624.4KAOFS::S_HYNDMANAcronym Decoder Ring ArchitectThu Oct 27 1994 12:4611
    
    
    	I beleive he is trying to determine what the IP address is from
    HUBwatch.  I noticed this as well.  The IP address of the MAM is
    displayed when you zoom in on a module in the hub.  It does not show
    you the address of the module itself.  The only way I found to display
    the address of the particular module in the hub was to choose it out of
    the community management table and view it like it was standalone.
    
    
    Scott
1624.5...More than one way to dance.... :-)NETCAD::BATTERSBYThu Oct 27 1994 13:085
    Oh I know what he's trying to do....he said that part clearly.
    I was just inquiring if he had determined in other ways whether 
    he could verify the addresses of each device.
    
    Bob
1624.6It is not supported.SLINK::HOODI'd rather be at the PenobscotThu Oct 27 1994 14:0312
    How's this for a definitive answer:
    
    The reason HUBwatch doesn't display the IP addresses of your modules is
    because it is not supported in the current versions of HUBwatch.
    
    There is work underway that will use a module's own IP address when
    managing it in a hub.  But that's a future version.  In the meantime,
    HUBwatch uses the MAM's IP address for almost all modules (DECservers
    and DECbrouters excluded; they must have their own addresses.)
    
    Tom Hood
    HUBwatch
1624.7NETCAD::SLAWRENCEFri Oct 28 1994 09:384
    
    The Hub Manager does not display the IP addresses of the modules on the
    LCD; it displays only its own in-band and out-of-band addresses.