Conference netcad::hub_mgnt

467.0. "DEChub 900 Token Ring Config?" by ANGLIN::CLAYTON (Merlin Clayton DTN 445-7217) Wed Nov 03 1993 18:24

I have a customer asking questions about integrating Token Ring into
his DEChub environment.  His current DEChub 90 configuration of looks 
like the following:

	  DEChub #1					 	DEChub #2	
	-----------------				    -----------------
	| | | | | | | |9|				    | |	| | | | | | |
	| | | | | | | |0|   Fiber Optic		 +-------+  | |	| | | | | | |
	| | | | | | | |F|========================|FO/10BT|--| | | | | | | | |
      |+|  {90TL} | | |A|   ~ 800 ft		 |  Xcvr |  |  {90TL} | | | |
      |	-----------------			 +-------+  -----------------	
      |	    Site #1						Site #2		
      |
      +
    +-----+
    |TL335|
    +-----+
       | 
       | T1
       |
    Central Backbone


The customer wants to add 8-16 Token Ring lobe ports to both Sites 1 & 2,
with the option to expand to more token ring at a later date.  He plans on 
running a Novell PC LAN on his token ring with the server being located
at the Central Backbone site.  To facilitate the Token Ring connectivity, 
would the following configuration work?


	  DEChub 90 #1					     DEChub 90 #2	
	-----------------				  -----------------
	| | | | | | | |9|				  | | | | | | | | |
	| | | | | | | |0|   Fiber Optic	       +-----+    | | | | | | | | |
	| | | | | | | |F|======================|FO/TW|---+| | | | | | | | |
      |+|  {90TL} | | |A|   ~ 800 ft	       | Xcvr|   ||  {90TL} | | | |
      |	-----------------		       +-----+   |-----------------	
      |	    Site #1					 |	Site #2		
      |							 |
      |(802.3)						 |(802.3)
      | +------+					 | +------+
      +-|DNX300|					 +-|DNX300|
      | +------+					   +------+
      |	      |						     |
      |	      |(802.5)					     |(802.5)
      |	      |						     |
      |	      | DEChub 900 #1				     | DEChub 900 #2	
      |	     -----------------				  -----------------
      |	     | | | | | | | | |				  | | | | | | | | |
      |	     | | | | | | | | |  			  | | | | | | | | |
      |	     | | | | | | | | |				  | | | | | | | | |
      |      | {900TL} | | | |   			  | {900TL} | | | |
      |      -----------------		       		  -----------------	
      |	         Site #1					Site #2		
      +
   +-----+
   |TL335|
   +-----+
      | 
      | T1
      |
   Central Backbone

In the above config, the DEChub 900 would provide the token ring connectivity
with 900 TL MAUs.  The 900 would connect to the Enet via a Proteon DNX 300
to provide routing of the IPX token ring traffic via Enet and the Vitalink
bridges that connect the remote facilities and the Central Backbone.  The
DNX 300 would be connected directly to a token ring lobe port on the 802.5
side, and would be daisy-chained to the existing DEChub 90 via thinwire on
the 802.3 side at site #2.  Same thing at site #1 with the addition of the 
VL TL335 to the Enet thinwire segment.

The IPX 802.5 traffic could then be routed onto the Enet segment via the 
DNX 300 at which time it would be bridged via the existing Vitalink bridges
to the Central Backbone where the server resides.

This all seems pretty kludgy to me, but it's the only way I can see integrating
this token ring environment via the DEChub 900.  

Will this congif work?

Is there a better way providing the TR integration than what I've shown here?

Any other alternatives are welcomed...

Thanks.

Merlin

			Is anybody out there??



What are the proper channels for configuration assistance for the DEChubs?

I need to find an answer for .0 ASAP.

Mgc

    I don't see any problems with what you are proposing.
    
    Are you going to run all the token ring nodes at the same speed?
    If some are at 4Mb and some at 16Mb you'll need to add interconnect
    between the two ( at tr-tr bridge ).
    
    I take it the existing DEChub90s are too full to just upgrade them to
    900s and add the token ring...

    
>>    Are you going to run all the token ring nodes at the same speed?
  
      Yes.  16Mb
    
>>    I take it the existing DEChub90s are too full to just upgrade them to
>>    900s and add the token ring...

      There are currently 5 & 6 modules in the existing DH90s respectively.

      When I looked at upgrading the DH90s to DH900s, it would require a
      repeater module of some sort (90FA?) to connect to the fiber backbone,
      an AUI connection to the Proteon B/router, and the Enet backplane 
      connection - three active interfaces on the repeater, which I don't
      think will work.  Is this correct?

      This is what led me to go with two separate boxes - the existing DH90
      and the addition of the DH900 for token ring only.

If there is a way of using the DH900 only, I would certainly prefer proposing
that as the solution.  Any creative ideas?

Merlin

    The DECrepeater90FA _is_ a three port repeater; you can repeat
    on _both_ front panel interfaces (fiber _and_ AUI) _and_ either the
    backplane or top connector thinwire at the same time.
    
    You may have been thinking of the DECbridge90FA, which looks the same
    and has the same interfaces, but has a switch between the fiber
    interface and the AUI; only one may be used at a time.

Thanks for the info on the repeater FA.  That certainly helps.

Mgc