Conference netcad::hub_mgnt

    
    Hello Jean-Yves,
    
    We just had the same Problem on a Customer Site here in Switzerland.
    Now we reproduced the Problem here in our Environment:
    
    -One DS90M in a single Stackable Hub connected via the Twisted Pair
     Port to the Network. Now it depends on, how the Position Identifier	
     Switch is set. If it is set in any other Position then "Agent",
     the DS90M Network Connection fails via the Twisted Pair Port!
     It makes also no difference, wheter the MGMT Cable is connected
     to it self, (MJ-8 Port in-out)
    -The behaviour is as follows: The DS90M makes its selftest, then
     loads its Image ether from Flash or from Network (depends on Type)
     does the Image Compression (ca 5Min) and when he is ready and
     loaded, the # Network LED goes out, and the Network Connection fails.
     That means: The Network connection fails after successfull load
     and decompression of the Image, over the Network! (or flash)
    -The only Solution we found is: Set the Position Identifier Switch
     to "Agent" so it works as the Stack Manager.
     Wheter this is Feature or Bug, i hope the Engineering for the
     Multistack Products knows the Answer...
    
     Daniel MCS Switzerland 

You might want to try the IROCZ::TERMINAL_SERVERS notesfile about this one.

Tom Hood

RE: .1

>    -The only Solution we found is: Set the Position Identifier Switch
>     to "Agent" so it works as the Stack Manager.

My recollection is that the DS90M software disables the 10BT port if the
DS90M is in a hub.  The External BNC is considered "disbaled" because of its
location (impossible to connect if the modules are adjacent).  The hub 
backplane 10B2 connection is used.  If the DS90M is standalone, then either 
the 10BT or 10B2 ports are usable (but not both).

It may be that any setting other than "agent" makes the DS90M want to use 
only the 10B2 port.  Just a guess.  I don't really know much about the stack
environment.  If someone could elaborate, then maybe I (or one of my 
compatriots) could have a look at the code to see what is happening.

Regards,

Dave

        Dave, 

        On the RoamAbout Access Point we discovered that the AP needs to be
        in a MultiStack slot number of nine or higher. This is due to the
        fact that the MultiStack essentially looks like a DEChub 90, split
        up if you will. So slots 1-8 make the module think it is in a DEChub
        90. In the case of the AP, in a DEChub 90 they disable the 10BT
        port and expect ThinWire (normally the backplane, but the
        external port works as well, and so it's fine in a MultiStack). 
        My suspicion is the the DS90M is doing something similar. 
        Set the slot switch to 9 or higher and I bet the 10BT port works.
        (Unless of course the DS90M supports the interconnected DEChub 90
        environment, in which case slots 9-16 are in the second hub...)

        Michael

    
    Hello Michael,
    
    The behaviour of the RoamAbout Access Point seems to be different
    to the DECServer 90M. I tried Position 9 and 14, but with no success.
    As soon as the Decompression has finished, the #LED goes off and
    the Network connection is terminated. (Connected to 10BT Port)
    
    Any other Ideas are wellcome,
                                            
    Daniel 

  Since i started this entry , i put 2 coins on the box...

  

  may be somebody from Decstack engeneering group could
  answered about the support of these configurations ?

  Jean-Yves