Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
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 |
HI, Can somebody validate the following configuration? I am a little bit confused with lobe and RI-RO port interconnection on a DEC900MS T.R. backplane. The Logical connection I would like to acheive is the following: ( ) ( ) ( ) ( ) (Local ring)-- F.O. Repeater--( Remote Ring ) ( ) ( ) ( ) ( ) | ___ === Enet/TR switch --- | --------+-------- Physically function should look as follow: +------------------------+ | Local IBM Ring | | | +-RI/MAU\RO+ +RI/MAU\RO-+ | | | | +-----------+ | | +---------+ | | | | .................................................... | | . RPTR RPTR SWITCH RPTR . | | . 900TL 900FL 900ET 90FS . | | . +---+ +---+ +---+ +---+ . | | . ----|-X-|--|-X-|-------|-X-|----| |-TR Channel . | | . | | | | | | | | . | | . ====| |==| |=======|=X=|====|=X=|=EnetChannel. | | . | D | | D | | D | | D | . | | . | T | | T | | E | | E | . | | . | R | | F | | T | | F | . | | . | O | | O | | E | | M | . | | . | R | | R | | R | | | . F.O. | | . | | | | | | | TX+------------.----------> | +--.-----+RO | | RO+----+ | TR+ | RX+----------->. To Enet Backbone +-------.-----+RI | | RI+--+ | | | | | . . | | | | | | | | | | . . +---+ +---+ | | | | +---+ . . | | | | 900MS . . | | +---+ . .................................................... | | F.O.| | | | | | +--+-+----------------+ | R R DTFOR R R | | O I O I | +-----------------+-+-+ | | +-----------------+-+-+ | **** **** DTMAU R R | | I O | +---------------------+ My main problem is the T.R backplane connection on the 900MS, (I don't have currently the equipment to test it). Should the RI/RO ports of the back of the repeaters be automatically interconnected together with one of the T.R. lobe port (redirected to the backplane) of the DECSwitch 900ET via the T.R. channel. Other concern is the speed. The ring should run at 16 Mbps, the speed is set up by switches on the Repeater, should they also select automatically the correct T.R. 16Mbps Channel. Thanks in advance, Robert
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3736.1 | NETCAD::GERHARDT | Out of Control | Tue Jul 23 1996 15:11 | 16 | |
>Should the RI/RO ports of the back of the repeaters be automatically >interconnected together with one of the T.R. lobe port (redirected to the >backplane) of the DECSwitch 900ET via the T.R. channel. the repeaters will connect to the backplane if there is an input signal on the front, or another TR device in the hub has an active signal. The DTMAU will only connect into the backplane if there is an active station attached to it. The DTMXM, since it has a MAC, always connects to the backplane. >Other concern is the speed. The ring should run at 16 Mbps, the speed is set up >by switches on the Repeater, should they also select automatically the correct >T.R. 16Mbps Channel. By default, 16 Mbps modules connect to Ring A and 4 Mbps modules connect to Ring B. These can be changed via HUBwatch/clearvision. | |||||
3736.2 | More info needed | NSDP01::RV | Wed Jul 24 1996 04:16 | 14 | |
I not quite sure if I was not clear with my question or if I have some difficulties to undertand your answer, so let me reformulate my question. Can a DTROR (back RI/RO) + DTFOR (back RI/RO) + a T.R. port of a DETER interoperate on a 16 Mbps T.R. backplane channel of a DEChub900MS under the condition that on both external (front RI/RO) of the repeaters are connected to RO/RI of DEC or NON DEC MAUs operating with ACTIVE stations running at 16 Mbps. If yes should I need to use CleaVisn to change the back repeater (DTROR and DTFOR) speed or will the front pannel switch be sufficient. Thanks in advance, Robert Vandenberghe | |||||
3736.3 | NETCAD::GERHARDT | Out of Control | Fri Jul 26 1996 12:25 | 2 | |
the only way to set the speed on a DTROR or DTFOR is via the switch. this can not be done from hubwatch/clearvision |