[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

1436.0. "Help on Hub900MS and Hubwatch V3.1 (DOS)" by DV780::MATSUSHITA (JA3QVP) Thu Sep 15 1994 18:08

    Hi,
    
    I just started to configure DECHUB900 MultiSwitch with HUBWatch for
    Window V3.1.
    
    In DEChub900SW (IP address 165.127.100.50),
    
    	-slot 8 ---- DECbridge 90FL with AUI calbe
    	-slot 7 ---- DECconcentrator 900MX (IP address 165.127.100.51)
    
    
    After I started HUBWatch for window V3.1, 
    I gave an IP address of hub900SW. Then I got the following message:
    
    	No response from the agent.
    
    So I used the  900MX IP address. I got the same result.
    
    When I ping these tow address, no response. I can ping other hosts on
    the network.
    
    Are these HW bad?
    
    Thanks for your help.
    
    nobuo
T.RTitleUserPersonal
Name		DateLines
1436.1Are you sureZPOVC::DAIV01::DANIEL_HDigital Astra NusantaraThu Sep 15 1994 23:1412
    Have you really got Hubwatch for Windows V3.1 ? Waoh ! I wish I had it,
    too.
    
    For capturing DECBridge 90 FL you need DECAgent 90 in the same LAN.
    
    From SPD V2.0 you can read, that it hasn't supported DECconcentrator
    900 MX yet only DECrepeater 900TM & DECserver 900TM.
    
    Rgds,
    
    Dnl
1436.2More infos pleasePADNOM::PEYRACHEJean-Yves Peyrache Country Support Group FranceFri Sep 16 1994 07:107
      re:0
       Have you designed the 900MX as IP services ??
       Which versions of Firmware  are you running (HUB,900MX)
       can you draw a little picture with you PC attached to
    
        Jean-Yves
1436.3The Price is RightLEVERS::DRAGONFri Sep 16 1994 08:2810
    
    RE:.1
    
    Daniel,
    
    	See note 1405.0 regarding HUBwatch for Windows V3.1 availability.
    
    Regards,
    Bob
1436.4Here is more info.DV780::MATSUSHITAJA3QVPFri Sep 16 1994 10:5825
    re:2
    
    I believe I set the IP service. I used "Hub 900 Multiswitch
    Installation Menu  option [8](Set In-Band Interface Address)".
    Do I have to do something else?
    
    The following are version information:
    
    	HW=F
        RO=V1.1.6
    	SW=V3.0.0
    
    Do I need to upgrade?
    
    
    I am using Compaq Deskpro 66m with DE205 (EISA config).
    
    From this PC, I can ping other system. I am using DOS V5.0 and Window
    V3.1. I just notice that DOS version is old. Do you think this is the
    problem?
    
    Thanks
    
    nobuo
1436.5What would prevent a 'ping' from working?CUJO::HILLDan Hill-NetConsultant-Denver-553-3624Fri Sep 16 1994 14:3020
    Why wouldn't a ping work for Nobuo in this situation?
    
    DEChub 900
    ---------------------                   X
    | DECserver 90TM	|                   |
    ---------------------                   *---HUBwatch PC
    | DECconc 900MX     |                   |
    ---------------------                   |
    | DECbridge 90FL  X-|-------------------*
    --------------------- AUI               |
    					    X
    
    The HUB Manager on the DEChub 900 in-band IP address is set to
    165.127.100.50 and the IP address on the HUBwatch PC is 165.127.100.25.
    
    He is unable to ping the DEChub 900.  Setup seems to be good.
    
    Any ideas?
    
    -Dan
1436.6Need IPS Module Connected to ThinwireLEVERS::DRAGONFri Sep 16 1994 14:4211
    
    Dan,
    
    >> Why wouldn't a ping work for Nobuo in this situation?
    
    A ping would not work if the IP Services Module was the DECconc
    900MX, which judging from the configuration shown might be the 
    case (ie DECserver 900TM and DECbridge 90FL cannot be IPS modules).
    
    Regards,
    Bob
1436.7Why ??????DV780::MATSUSHITAJA3QVPMon Sep 19 1994 11:3712
    Bob,
    
    Can you explain why the DECconc 900MX would not server as the IP
    Services Module?
    
    Because this DECconc 900MX is FDDI moduloe, but we are not using FDDI ?
    
    
    Thanks in advance
    
    nobuo
1436.8NETCAD::DRAGONMon Sep 19 1994 11:5717
    
    Nobuo,
    
    	The PC is connected to the DECbridge 90FL and if my assumption is
        correct, your IP Services Module is the DECconcentrator 900MX. The
        IP Services module lends the MAM its MAC, since the MAM does not 
        have its own. So the IP address gets associated with the MAC of the
        DECconcentrator 900MX, which your PC cannot see or reach, given the
        modules shown. You could accomplish what you desire if the bridge
        were a DECbridge 900MX (aka DECswitch 900EF) and it was configured
        to bridge the Ethernet that the PC is on and the FDDI LAN that the
        DECconcentrator 900MX is on. You could also connect your PC to the
        DECconcentrator directly. In short, for In Band to work your NMS must
        have network connectivity to the IP Services module. 
    
    Hope that's clearer,
    Bob
1436.9NETCAD::GALLAGHERMon Sep 19 1994 15:2712
You might also be able to connect your MAM out-of-band management port
to your terminal server.  If you configure the terminal server port
for SLIP services, and connect that port to the management agent module's
out-of-band, and your server is reachable, then your PC can reach the MAM 
via Ethernet.

(I don't know for sure if your terminal server supports SLIP.)

Doing this defeats the purpose of out-of-band management since your depending
on your regular network.  It does, however, allow the hub to be manageable
using your configuration.
						-Shawn