| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 3349.1 | yes and no | KAOFS::R_YURKIW | reward those who bring bad news!! | Mon Mar 11 1996 15:44 | 10 | 
|  |     The hub will Automagically connect the 90TS to the flex channel on the
    upper connector. You don't have to worry about which one it is.
    
    As far as adding a second card you could only connect it to the same
    flex channel as the first one because it also must be on the upper flex
    channel. 
    
    regards
    
    Roger
 | 
| 3349.2 |  | NETCAD::HERTZBERG | History: Love it or Leave it! | Mon Mar 11 1996 15:48 | 22 | 
|  |     When you instruct the hub to connect the 90TS to one of your configured 
    LANs, the MAM is smart enough to know that for the connection to be
    possible, the LAN will have to be on the flex channel on the upper 
    connector (the only flex channel the 90TS can attach to).  If the LAN
    you want to attach the 90TS to isn't currently mapped to the flex
    channel on the upper connector, the MAM will attempt to shuffle around 
    the mapping of LANs to flex channels in the hub to achieve your desires.  
    It may or may not be able to do this, depending on the current 
    configuration of the hub.
    
    >>  ... can I have another DECrepeater 90TS in the next slot connect 
    >>  to a different Flex Channel Lan?
    
    Definitely not.  The 90TS can only attach to the flex channel in the
    upper connector.  So if two 90TS in the same hub are both attached to
    flex channels, then they're both attached to the same flex channel (the
    one in the upper connector) and therefore are on the same LAN.
    
    The only way for two 90TS in the same hub to be on different LANs is
    for one to be on the flex channel in the upper connector and the other
    to be on the thinwire.
    
 | 
| 3349.3 | Customers ask about these things. | ALBANY::BARTLEY |  | Tue Mar 12 1996 14:05 | 6 | 
|  |     Is there any way looking at HUBwatch to identify the flex channel in
    the upper connector? Maybe in a future release of Hubwatch/firmware?
    
    Thanks
    
    Dave
 | 
| 3349.4 | LAN interconnect does NOT indicate flex0 | NETCAD::MOWER |  | Wed Mar 13 1996 14:14 | 24 | 
|  |     
> Is there any way looking at HUBwatch to identify the flex channel in
> the upper connector? Maybe in a future release of Hubwatch/firmware?
    
    Virtually no.  Almost definitely no.
    
    The only way you could determine which [HUBwatch LAN interconnect] LAN
    represents flex0 [in the hub900] would be if you had a 90FS/TS
    successfully connected to a [LAN interconnect] LAN.  Since the MAM will
    only permit the 90FS/TS to be connected to flex0, such a LAN would thus
    have to be flex0.  This is really just a backwards way of re-phrasing
    the rule that two or more 90FS/TS can only be connected (except using
    Thinwire) via a common [green] LAN.
    
    There are no plans to inform the user about any correlation between the
    LANs they see [in HUBwatch's LAN interconnect screen] and the flex
    channels [in the hub900].  In fact, in the future we'd like to distance
    the customer from the details of the hub's flex channels even more.
    
    Aside from the 90FS/TS rule stated above, is there any other reason the 
    customer should be concerned about what specific flex channels are used 
    by the MAM to build their LANs?
                                                               Carl.
    
 | 
| 3349.5 | The MAM Shuffle | ALBANY::BARTLEY |  | Wed Mar 13 1996 16:21 | 10 | 
|  |     Thanks for the reply Carl. 
    
    If a customer has a DEChub 900 with some 900 repeaters connected to a
    few flex channel ethernets, and they add a 90TS and want to connect it
    to a particular LAN group....Will the MAM shuffle aound the flex
    channel configuration to make the connection?
    
    Thanks,
    
    Dave
 | 
| 3349.6 | The MAM two-step | SLINK::HOOD | Your bad news bear | Wed Mar 13 1996 16:36 | 3 | 
|  | Yes.  The MAM will do the right rearranging if possible.
Tom
 |