Conference netcad::hub_mgnt

    
    Andrew,
    
    	GIGAswitch/FDDI Hunt Groups are supported in MCM V5.0. The behavior
        which you see with the physical port's icons going red is expected
        behavior. There has been some discussion about changing this
        behavior and using a neutral color. The way in which you can 
        distinguish this red port as being a port with bad status vs a
        hunt group member port is by the text in the description field
        next to the port, which says that it is a member of a hunt group.
        You would then want to check the status of that hunt group port
        and as you have done check the hunt group members window, which
        bases its status on hunt group versus bridge port specific MIBs.
        Any suggestions on improvement here would be welcomed.
    
        Traffic groups are not yet supported by MCM. It is on the list.
    
        Not sure on the last item. The GIGAswitch notesfile may already 
        have a list somewhere.
    
    Regards,
    Bob

        ...traffic groups are documented in the BL3.0 release notes and in
    the new GIGAswitch MIB,  however this won't help you much trying to set
    them up via MCM V5.0.
    
          <<< SCHOOL::CLUSTERFILES:[NOTES$LIBRARY]GIGASWITCH.NOTE;1 >>>
                                -< GIGAswitch >-
================================================================================
Note 551.2               HUNT Group Protocols Supported                  2 of 14
NPSS::MDLYONS "Michael D. Lyons DTN 226-6943"        13 lines  14-AUG-1995 10:33
--------------------------------------------------------------------------------
        Is is not whether or not a protocol is supported, as the previous
    reply suggests - all protocols are supported.  The point of interest is
    which protocols are defined (by default) as multipath protocols.
    
    XLII (old DEC spanning tree)
    IP
    IPX
    ARP
    ISOCNLS
    DECnet Phase IV
    NISCS

    ...are multipath protocols
                                                                        

    re .1/.2,
    
    thanks for your answers.
    
    In the default multiple-path protocols list LAT, MOP and SCA 
    (VAXcluster traffic) are not there,
    does it mean Gigaswitch (with HUNG group enabled) will ONLY send LAT
    and MOP to one of the members of the HUNG group, will it be the FIRST
    one of the member?
    
    Customer will use TWO E3 (once they are available) to interconnect two
    data centers via Gigaswitches, so SCA (VAXcluster traffic) is very
    important work with HUNT GROUP, will SCA be supported over HUNT GROUP,
    is yes, how can add SCA to the multiple-path protocols list?
    
    thnaks in advance for help!
    Andrew Chiu - Network services Sydney 

           ...these questions belong in SCHOOL::GIGASWITCH, but to save a
    little time, I'll answer here...   first of all we prefer to call them
    "hunt" groups, not "hung" groups - people might get the wrong idea....
    
        SCA is on the list - NISCS = SCA.  
    
        For single path protocols like LAT, the default behavior is that
    when the hunt group is initialized by the two GIGAswitch/FDDI systems,
    they decide which port they'll send single path traffic over, and it
    stays that way until the port goes down.  If the port goes down, the
    single path port will switch to another port.  You can not generally
    make a statement that it will be the "first" port in the hunt group. 
    Actually, there is no easy way for you to figure out which port is
    being used for single path traffic.
    
        You can do primitive load balancing of single path traffic by using
    traffic groups.  This allows you to group input ports together to use a
    common single path output port.  See the BL3.0 release notes or look in
    the SCHOOL::GIGASWITCH notes conference for more information.
    
    MDL

    re .4,
    
    Thanks for your quick answers.
    
    Andrew