| 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 | 
Hello,
    
I looked through the notesfile entries and could not find an answer to my 
question. I will copy and read the manuals, but could somebody please
     clearup my confussion surrounding the total number of 
supported Token-Ring channels on the DEChub 900 MultiSwitch? 
1) In calling Colorado support, I was told 2 channels, but there was 
   currently a problem with one of them and therefore a 'safe answer' 
   was 1 channel. 
2) In looking at the original sales update it had a competition chart 
   showing our product against other vendors hubs, and it listed a total 
   of 16 possible Token-Ring channels. 
3) Finally, there is a new powerpoint presentation (pretty good) on
   NAC that has one sheet showing the top half of the DEChub 900 as 
   "2 Etherent, 2 Token-ring" and the bottom half as "14 felxible LAN 
   technology channels, supporting Ethernet, Token-Ring, FDDI, and ATM 
   ready". Yet a couple pages later, they list the DEChub 900 as 
   "Supports up to (16) Ethernets, (2) Token-Rings, (7) FDDI"
Any takers? What is the supported answer today?
Thanks for the help.
Garry
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 480.1 | QUIVER::SLAWRENCE | Tue Nov 09 1993 11:58 | 20 | ||
|     There are 2 dedicated token ring channels on the upper connector of the
    900.  These are called Ring A and Ring B.  By default, one is 4M and
    one is 16M; the token ring modules will be inserted on the ring whose
    speed they match.  If you want to use both at the same speed (creating
    two unconnected rings, unless you are connecting them somehow outside
    the hub), then this is possible via SNMP but that is not supported by
    the current version of HUBwatch.
    
    The flexible channels _could_be_ used for token ring, but no existing
    modules do so.
    
    The presentation should be:
    	Top connector:
    		1 dedicated Thinwire (DEChub90 compatible)
    		1 Flexible channel
    		2 Token Rings
    
    	Bottom connector:
    		14 Flexible channels
    
 | |||||