[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

2818.0. "General Questions on using the PortSwitch modules..........." by KERNEL::CHOPRAA () Mon Oct 02 1995 05:47

Hi,

I have a customer who has just purchased a PortSwitch 900CP and is trying to
configure it.  Neither my customer or myself are having any luck finding the
necessary information.  Please could someone help by answering the following
questions (for starters!).

1.  In the Port Switching window, what is the purpose of assigning the thinwire
to a group?  Does this not cause a loop when connecting the group to another
lan?

2.  In the same window, what effect does assigning the MAC to a group have? 
What is this option used for?

3.  In the main Repeater Summary Window, what effect does disabling the
backplane port have. On a non switching repeater, this would isolate the
repeater from the rest of the hub.  On a PortSwitch, this functionality seems 
a little redundant.

Any information would be appreciated.

Regards

Anil Chopra                             Tel:  01256-373746 (Direct line)
UK Comms Support                        DTN:  7833-3746
Digital Customer Support Centre         Fax:  01256-841494
Multivendor Customer Services           Internet:  [email protected]
T.RTitleUserPersonal
Name		DateLines
2818.1NETCAD::DRAGONMon Oct 02 1995 09:5527
    
    Anil,
    
    
    1. Assigning the thinwire to a group is similiar to assigning a port to
       a group. Think of the thinwire as another port which already has 
       media attached and is internal to the DEChub.
    
       A loop will not result if you connect this group to another LAN, if
       you do not have another repeater on that same LAN, which is also 
       connected to the thinwire. HUBwatch has code to detect loop
       conditions made internal to the DEChub. External (physical)
       connections are up to the user to manage.
    
    2. Assigning a MAC to a Port Group causes the PORTswitch to recognize
       packets on that Port Group which are destined to it. It will not
       respond to packets destine to its MAC on those Port Groups which
       do not have the MAC assigned.
    
    3. This function is a bit redundant in that it is similiar to
       disconnecting the thinwire on the LAN Interconnect window.
       Internally it is handled a bit differently, but same effect in that
       no traffic is passed onto/received from the thinwire. You can also
       assign the thinwire to "no connection" on the Port Switch window.
    
    Regards,
    Bob