[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

3223.0. "4.1-1,4-1-2 hubwatch,routeabout telnet sessions." by KERNEL::SMITH_P () Thu Feb 01 1996 09:42

    Hi,
        I have a customer unable to make the telnet connections from within
    a hubwatch 4.1-1 window to his new Routeabout boxes. A window appears
    but the connection does not complete. I have, however, been able
    to make this type of connection using 4.1-2. Does the "-2" indicate
    that this is a patched or new version? If patched, will an ECO kit be
    available? I am reluctant to advise him to purchase 4.1-2 if it does
    not provide further improved Routeabout support that I understand is 
    coming in v5.*.
    
    Thanks,
    Paul.
T.RTitleUserPersonal
Name		DateLines
3223.1No. Wait until 5.SLINK::HOODThey call me MISTER Dilbert.Thu Feb 01 1996 12:5821
    No, there are no patched updates to HUBwatch. Your customer will see
    exactly the same symptoms will every 2.* thru 4.* version of HUBwatch.
    
    TELNET launching in HUBwatch 4.* (and before), as your customer has
    noticed, has a problem. What's happening is the code that does the
    remote address determination always picks the highest numbered IP
    address for the router. Unfortunetly, it  includes the DEChub MAM's IP
    address in that list, because it's merely trying to find the management
    agent for the device. Trust me, for everything (except TELNET) this
    scheme works.
    
    My guess is that when you try doing it in your office, you're assigning
    a different set of IP addresses to the router, and/or have a different
    address on the MAM. If you duplicate your customers addresses, you'll
    see the same feature.
    
    Version 5 of HUBwatch corrects this problem, and makes life in general
    a little nicer for router owners.
    
    Tom Hood
    (the person who put the "imagination" into TELNET).
3223.2thanksKERNEL::SMITH_PThu Feb 01 1996 13:384
    Tom
        many thanks, I'll take your advice.
    
    Paul.
3223.3Possible workaround?LEMAN::PAIVAHawkeye - Network Support @GEOTue Feb 06 1996 07:3018
    Tom,
    
    >   TELNET launching in HUBwatch 4.* (and before), as your customer has
    >   noticed, has a problem. What's happening is the code that does the
    >   remote address determination always picks the highest numbered IP
    >   address for the router. Unfortunetly, it  includes the DEChub MAM's
    >   IP address in that list, because it's merely trying to find the
    >   management agent for the device. Trust me, for everything (except
    >   TELNET) this scheme works.
      
    Do you mean by this that assigning the MAM the LOWEST IP address of all
    that hub's address (ie. MAM and modules' addresses) would be a
    workaround?
    
    Thanks.
    
    Pedro
3223.4Exactly!SLINK::HOODThey call me MISTER Dilbert.Tue Feb 06 1996 12:318
>    Do you mean by this that assigning the MAM the LOWEST IP address of all
>    that hub's address (ie. MAM and modules' addresses) would be a
>    workaround?
    
    Exactly. Sorry I wasn't clearer on that point. Then the TELNET
    connection will be made to the highest router IP port address.
    
    Tom