[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

532.0. "In-band & OOB Concurrently?" by HGRNCC::FARADAYCHONG (Faraday Chong@hgo 852-8053590) Wed Dec 01 1993 09:53

    Need clarification on using both in-band and out-of-band (OOB)
    management simultaneously on a hub. It is likely that we use in-band
    to monitor and detect if path failure to the hub, and control the hub
    via OOB to trigger external events. This requires communicating to the
    agent both in-band and OOB.
    
    Are there any problems with DEChub 900?
    
    What is for DEChub 90 with DECagent 90 (and DECbridge 90)?
    
    Faraday
T.RTitleUserPersonal
Name		DateLines
532.1Concurrent In-band & OBM OKQUIVER::SLAWRENCEWed Dec 01 1993 12:2416
    The hub can use In-band and OBM concurrently with no problem; we do it
    all the time.  This does require two different IP addresses for the hub
    (as with any multiple-interface IP device). 
    
    I believe that the only way to switch from one address to another from
    HUBwatch is to manually select a new entry in the agents table (it does
    not fail over automatically) [Go ahead, Bob, correct me if I've got
    that wrong - don't worry about my feelings :-)].  I think that this is
    actually a good idea because the user knows what HUBwatch is doing.
    
    The V1.1 DECagent 90 does not support any OBM; V2.0 will add it (SLIP
    over the console port).  Note, however, that the communication between
    the DECagent and the DECbridge is always In-Band.  While the V2.0
    DECagent will not need a DECbridge to manage a hub it is plugged into,
    if the network is too bad it may not be able to communicate well enough
    with the bridge to manage a remote hub.
532.2Scott is correct no automatic failoverQUIVER::HAROKOPUSWed Dec 01 1993 13:1517
>        I believe that the only way to switch from one address to another
>    from HUBwatch is to manually select a new entry in the agents table (it
>    does not fail over automatically) [Go ahead, Bob, correct me if I've got
>    that wrong - don't worry about my feelings :-)].  I think that this
>    is actually a good idea because the user knows what HUBwatch is doing.
    
    No need to hurt your felling because you have it correct :-).
    HUBwatch will use always use the IP address specified
    by the user to manage the hub and any modules that can be managed
    through the hub manager's gateway.   The only way to switch between
    OBM and IBM is through the agents table.
    
    We are looking into providing automatic failover in a future release.
    
    Regards,
    
    Bob