[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::atm

Title:atm
Moderator:NPSS::WATERS
Created:Mon Oct 05 1992
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:970
Total number of notes:3630

877.0. "DigiUNIX's BUG in cut VC ?" by HGOM19::MARKWU () Fri Mar 21 1997 22:05

    Hi, colleagues:
    
    	I meet a problem in ATM with DigiUNIX 4.0B.
    
    	--------|       |--------------|
        |Server |-------|GigaATM switch|
        | 4.0B  |       |--------------|
        --------|           |     |
                            |     |
                      Master|     |Slave
                            |     |
                         ===================
                         |  DECSwitch 400  |
                         ===================
    
    
STEP 1: When i disconnect the master ATM link, 
    	the Slave link will backup the Master link. in the LE-ARP level.
    	It is say, the ATM-address will change, but the MAC address is
    	the same. and VC will rebuild.
    
STEP 2:	But if I reconnect the Master link, I can see the Master will
        rebuild VC, the slave will disconnect the VC, and LE-ARP have a
    	replace, the MAC address is not change but the ATM-address will 
    	be replaced by master ATM link.
    
    	The strange is in STEP 2, once the slave VC disconnect, 
    	Alpha Server(DigiUNIX 4.0B) will dead, no dump, no any prompt,
    	the Server's network becames unreachable, the screen looks like locked,
    	I cann't move mouse, key the keyboard is no use......
    
    	So, when I reconnect the master link, I must down the IP in ATM
    	netcard, wait 1 min. UP the IP in ATM-netcard. NOW it is OK !
        I believe it is a software BUG in UNIX. Is it true?
    	Or I mistake some config ?
    
                                                                    
T.RTitleUserPersonal
Name
DateLines
877.1Known problem - stay tunedSMURF::GREBUSDTN 381-1426 - Digital UnixMon Mar 24 1997 15:486
    A bug that could cause this behavior was discovered recently.  There
    should be a patch available by the end of this week.
    
    	/gary