[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

627.0. "HUBwatch config ?? for customer" by SPANKY::PETROFF () Mon Jan 17 1994 13:23

    
    A customer is proposing a configuration that has 5 DEChub 90's 
    daisy-chained together. A sixth DEChub 90 is connected by fiber
    through a DR90FA in one of the original 5 hubs. Three questions
    with regard to HUBwatch:
    
    1) How many DEcagents are required to support this config?
    
    2) How many bridge modeules are required to support this config?
    
    3) Is it possible/recommended to have a dial-in line connected to the
    agent?
    
    
    Thanks,
    Rick

T.R Title User Personal
Name Date Lines

627.1 How do you plan to Daisy-Chain 5 Hubs?? MSDOA::REED John Reed @CBO, DTN:367-6463, KB4FFE, SouthEast Mon Jan 17 1994 14:14 43

T.R	Title	User	Personal Name	Date	Lines
627.1	How do you plan to Daisy-Chain 5 Hubs??	MSDOA::REED	John Reed @CBO, DTN:367-6463, KB4FFE, SouthEast	`Mon Jan 17 1994 14:14`	43
	It depends how you define >> 5 DEChub 90's daisy-chained together <<. Some Basic Rules: You Need ONE BRIDGE module to control the Hub Management Bus (until the V2.0 Software for the DECagent comes out) of every HUB. When I say "HUB" in capital letters, the HUB can be either: a) an 8-slot HUB, (created by Installing a single DEChub90 backplane, with a terminator in the Side ThinWire Port) or b) a 16-slot HUB (created by using Two DEChub90 Backplanes, and connecting them Together using two cables. One Cable is the ThinWire backplane extention, (No other Devices can be connected to this cable, and it is not to exceed 55 meters). The second required cable is the 6-pin MMJ cable to extend the management bus. You Also need One DECagent 90 Module to control every 4 bridges. Once the V2.0 DECagent Code is available, then you can use the DECagent as the Bus manager (one Per HUB), but I prefer using a Bridge, because of the traffic isolation, and protocol filtering, and MAC address tracking. I assume that you understand that you cannot create a 40-slot HUB, by daisy-chaining 5 DEChub90s together... I don't understand from your description how the 5 primary DEChub90's are configured. But you DEFINATELY need a Bus master module for the remote DEChub90 connected by fiber. I would suggest the DECbridge90FL, which will provide the fiber link, and the bus management. If the first FIVE DEchub90's are configured as two 16-slot HUBs, and One 8-slot HUB, then you will need THREE BRIDGE modules to control them. You can attach a DECagent 90 to any HUB (need slot 7 or 8) and it will be able to provide the management software conversion for all of your HUBs. I have not needed to remotely log into the Agent, using a modem line. Once the DECagent is configured, it usually just works. If you are nervous, you can devote a Terminal server port to the DECagent console, or you can put a dedicated Modem on that port. Either way will work. I hope that helps. JR

    It depends how you define >> 5 DEChub 90's daisy-chained together <<.
    
    Some Basic Rules:
    You Need ONE BRIDGE module to control the Hub Management Bus (until the
    V2.0 Software for the DECagent comes out) of every HUB.  When I say
    "HUB" in capital letters, the HUB can be either:
    	a) an 8-slot HUB,  (created by Installing a single DEChub90
           backplane, with a terminator in the Side ThinWire Port)
    or
    	b) a 16-slot HUB (created by using Two DEChub90 Backplanes, and 
    	   connecting them Together using two cables.  One Cable is the 
    	   ThinWire backplane extention,  (No other Devices can be
           connected to this cable, and it is not to exceed 55 meters).  
    	   The second required cable is the 6-pin MMJ cable to extend 
    	   the management bus.
    
    You Also need One DECagent 90 Module to control every 4 bridges.  Once
    the V2.0 DECagent Code is available, then you can use the DECagent as
    the Bus manager (one Per HUB), but I prefer using a Bridge, because of 
    the traffic isolation, and protocol filtering, and MAC address tracking.
    
    I assume that you understand that you cannot create a 40-slot HUB, by
    daisy-chaining 5 DEChub90s together...   I don't understand from your
    description how the 5 primary DEChub90's are configured.
    
    But you DEFINATELY need a Bus master module for the remote DEChub90
    connected by fiber.  I would suggest the DECbridge90FL, which will
    provide the fiber link, and the bus management.  
    
    If the first FIVE DEchub90's are configured as two 16-slot HUBs, and
    One 8-slot HUB, then you will need THREE BRIDGE modules to control
    them.  You can attach a DECagent 90 to any HUB (need slot 7 or 8) and
    it will be able to provide the management software conversion for all
    of your HUBs.   
    
    I have not needed to remotely log into the Agent, using a modem line. 
    Once the DECagent is configured, it usually just works.  If you are
    nervous, you can devote a Terminal server port to the DECagent console,
    or you can put a dedicated Modem on that port.  Either way will work.
    
    I hope that helps.
    
    JR