[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

2898.0. "PESwitch900TX loosing connections?" by DRAC::DSMAIL () Mon Oct 23 1995 13:33

    
    
    Hi,
    
    Last week-end I've installed/configured a DECHub900 with the following
    configuration:
    
    3*PortSwitch900TP
    1*DECSwitch900EF and
    1*PESwitch900TX
    
    I tied the DECswitch to the PESwitch via an internal FDDI dual ring,
    and I left the PESwitch for attaching the Novell Servers, AS400s and
    moreover we connected two single PCs to the empty PEswitch inputs.
    
    The AS400 and the Novell Servers communicate with their clients without
    any problem at the first try.Customer (and me happy),
    but the two PCs connected directly to the PESwitch had to reboot twice
    to get into the network...a timeout occurred.
    I assumed and I then said to the customer that should be a timeout expired
    due to the bridge in the learning state....ok let's see on monday...ok
    bye bye...
    
    On monday -today- I receive a phone call from them....
    
    Once these two PCs have had accessed to the net suddenly they loose the
    connection to the AS or to the Novell server....if they reboot the PCs
    they get access to the network again and so on...
    
    What's posibly happening?
    
    The customer has told me that when he looses connection, the PEswitch
    port where the PC is connected Hubwatch shows a ear...I assume the PEswitch
    is in the learning state...I'm wrong?
    But why they loose connections while they are connected?
    Does the PEswitch or the DECswitch have a forwarding data table that flushes
    out old addresses with no activity ? or there is something else..., let's
    say: a bug...
    
    All modules run the latest rev of firmware (4.1.1) with Hubwatch 4.1.1.
    
    Any clue ?
    
    Thanks in advance
    
    Jordi Manchon
    NS Barcelona -SPAIN-
           
T.RTitleUserPersonal
Name
DateLines