[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

3683.0. "Hubwatch System Error on Gigaswitch" by GIDDAY::KULHALLI () Mon Jul 08 1996 03:46

    
    I have a customer problem using hubwatch 4.1 to manage Gigaswitch/FDDI.
    He is able to get the hubwatch display of the front panel. Later he
    clicks on the SCP module ( or FGL2 module) and receives an error
    message "System Error". This happens on two of the four Gigaswitches
    that he has in the network.
    When he clicks on the SCP module he expects to get summary window -
    instead he receives the error mesaage. This happens on hubwatch 4.1
    on Windows and OSF platforms.Basically he cannot manage the two of
    those Gigaswitches.
    He has observed similar problem managing some of the 900EF moduiles
    in the network. w-db900snmp error;No data received;SUM-U error.
    
     These errors indicate to me - he is able to load the front panel -
     using SNMP - but unable to use the snmp to further manage/click on
     a module to display the summary window. 
     The hubwatch is sending - lots of snmp commands - but does not receive
     reply back from the Gigaswitch/FDDI.
     
     Customer does not want to reboot to Gigaswitch - which may fix this
     problem 
    
     Any feedback on this welcome.
    
     Cross posted in Gigaswitch/FDDI notes conference. 
    
     /mohan kulhalli
      csc sydney
T.RTitleUserPersonal
Name		DateLines
3683.1GIDDAY::KULHALLITue Jul 09 1996 18:0122
    
    I am not sure whether I have been clear enough in my previous note,
    I went onsite and connected the my laptop to the Gigaswitch directly
    thru. a standalone 900EF and I could get the front panel loading
    successfully - however following that I double clicked on SCP
    module which resulted in "system and general error". 
    Next I double clicked on the FGL4 line card which gave me the summary
    window - next I double clicked on Bridging - whicg again resulted in 
    "system and general error".
    Next we rebooted the Gigaswitch and that cleared the problem.
    Similar problem was observed on hub 900 modules at different locations
    which are cleared by reseating the module .
    Is this a bug in hubwatch 4.1 or the Gigaswitch/various hub 900
    modules ?
    We are using hubwatch 4.1.1 and 2.2 of Gigaswitch and all 900 modules
    are at latest rev.
    
    Thanks for any feedback.
    
    /mohan kulhalli
     CSC Sydney
3683.2NETCAD::DRAGONWed Jul 10 1996 09:129
    
    Mohan,
    
    	This is a bug in HUBwatch in the fact that we should not crash.
        Do you know how long the GIGAswitch had been up without a reboot?
        There was a problem with sysuptime exceeding 32 bits. That's one
        possible explanation.
    
    Bob
3683.3Need Fixed version of HubwatchGIDDAY::KULHALLIWed Jul 10 1996 17:3614
    
    Bob,
    
    I am not sure for how long but - is this bug fixed in multichasis
    manager release 5.0 on clearvision ?
    Please treat this urgent as customer has another Gigaswitch exhibiting
    similar problem and customer is very reluctant to power cycle the
    Gigaswitch as that would bring the entire cluster and hence the
    whole hospital down for more than a hour.
    Any quick feedback is most welcome.
    
    Thanks foe your support.
    
    \mohan
3683.4NETCAD::DRAGONThu Jul 11 1996 13:098
    
    Hi Mohan,
    
    	A problem with sysuptime was corrected in MCM V5.0. It sounds like
        this could be what you are running into.
    
    Bob