[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

1035.0. "HW/Windows and LAN Interconnect questions" by DPDMAI::DAVIES (Mark, SCA Area Network Consultant) Thu May 26 1994 14:00

    I have a DEChub 900 in the Dallas ACT.  Two of the modules in this unit
    are a DR900TM (slot 8) and a DS900TM (slot 1).  I have the ability to
    manage all modules in the hub successfully.  I can do everything that
    you would expect until I get to the LAN Interconnect window, and then
    things get ugly on me (or maybe I get stupid).  
    
    Here are the actions I am seeing and wonder why:
    
    1. I can connect EITHER port 1 or 2 of the DS900TM to any IMB I have
       created,  But I cannot connect both ports at the same time to a
       single DH900 IMB or different IMBs.  The HW for Windows Manual V2
       says this should be possible.
    
       I get the message in a little window which states:
    
    		 HUBwatch: Error
    
    		 Add Failed
    
    2. The DR900TM has port #1 connected to the thinwire.  Anytime that I
       attempt to connect port #2 to an IBM I get the following message:
    
    		HUBwatch: Confirmation Window
    
    		This connection may result in a loop.  
    		Do you want to continue?
    
       It is obvious to me that a loop will not be created, but not to 
       HUBwatch.  I am making the connection to a IMB which has no other 
       connections.  Why does it ask this question?
    
     3. If I have port #2 of the DR900TM connected to an IMB, I cannot
        connect either port of the DS900TM to any of the IMBs or to the
        thinwire backplane, ie, I cannot connect the DS900TM to anything.
    
        Also, the DS900TM comes up defaulted with both ports connected to
        the thinwire segment.  If I disconnect either port from the
        thinwire segment, I can not reconnect it.  I can connect it to an
        IBM segment.
    
    	In both of the above cases, I get:
    
                     HUBwatch: Error
    
                     Add Failed
    
    Am I missing something somewhere?  Is these product bugs or operator
    bugs?
    
    Thanks,
    
    Mark
T.RTitleUserPersonal
Name		DateLines
1035.1Both HUBwatch for Win & VMSDPDMAI::DAVIESMark, SCA Area Network ConsultantTue May 31 1994 09:2021
    I have now tried .0 from both HUBwatch for Windows V2.0 and HUBwatch
    for OpenVMS V3.0 and it still doesn't work.   If I take the DECserver
    900TM out I can configure the the DECrepeater 900TM anyway the I would
    like.  
    
    Is this a known bug?
    
      DR900TM Summary Window states: HW=v2, RO=v1.
    
      DS900TM Summary Window states: NAS V1.3, BL80-27 ROM V5.0-0 LAT V5.1
    
      The DEChub 900 is: HW=F, SW=V2.2.1
    
    We are going to give some demos this week.  Any assistance on this
    would be appreciated.
    
    Thanks,
    
    Mark
1035.2Some PossibilitiesLEVERS::DRAGONTue May 31 1994 11:3016
    
    Mark,
    
    	If you have another DS900TM available you may want to try different
        hardware. What you described does not sound like pilot error. As
        for the warning about possible repeater loops, this is expected
        behavior. HUBwatch warns the user because with some modules
        repeater loops are not detected (ie DR900FP).
    
        One possible source of your IMB connectors not sticking is that you
        have exceeded 6 Ethernet IMBs. You are allowed to create more than
        6 Ethernets, but only 6 will work with the DR900TM hardware. You
        may want to double check on this with your configuration.
    
    Regards,
    Bob
1035.3No luckDPDMAI::DAVIESMark, SCA Area Network ConsultantTue May 31 1994 12:3110
    I deleted all but 3 IMBs.  The main problem still exists, ie, we cannot
    connect the ports of either the DR900TM or DS900TM to an IMB when the
    other already has one port connected to an IMB.
    
    I don't have additional hardware to try this out.
    
    Regards,
    
    MArk
1035.4SOmeone tell me they have done it!DPDMAI::DAVIESMark, SCA Area Network ConsultantWed Jun 01 1994 09:3712
    Let me get someone to at least verify that they have infact TRIED and
    successfully connected, simultaneously, port #1 of a DECserver 900TM to
    an IMB and port #2 of a DECrepeater 900TM to an IMB.
    
    If you have, please give the hardware and software revision numbers of
    your equipment.  We need to get a fix for this.  The customer wants to
    see this configuration demoed - successfully.
    
    Thanks,
    
    Mark
1035.5Been there. Done that.LEVERS::DRAGONWed Jun 01 1994 12:1111
    
    Mark,
    
    	I've tried this using the following:
    
        DETMM-M REV B01 HW=V2, RO=V1, SW=V1.0Ib001
        DSRVZ-M REV A01 NAS V1.3 for DS900TM BL80-27, ROM V5.1-0
        DEChub 900 MAM HW=F, SW=V3.0.0
    
    Regards,
    Bob
1035.6REVsLEVERS::DRAGONWed Jun 01 1994 13:567
    
    Mark,
    
    	I believe that DETMM with SW=V1.0G,H,or I should not matter as well as
        DSRVZ with ROM V5.0-0. I would suspect bad hardware.
    
    Bob
1035.7been there, fixed itUFP::LARUEJeff LaRue: U.S. Network Resource CenterFri Jun 03 1994 12:0310
    Hi Mark,
    
    We had similiar problems here at Westinghouse......the solution was
    to upgrade the DEChub MAM firmware to the one found on the consolidated
    kit.
    
    ...after that we can move those little module tails anywhere we want
    to!
    
    -Jeff