[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

1395.0. "900FP Resets?" by LARVAE::FROST_J () Thu Sep 08 1994 17:48

    Hello there,
    
    I have a customer running DECrepeater 900FP's in DEChub 900 MS's, they
    have been having problems with LAT disconnects, and LAVc nodes hanging
    since these were installed, and have noticed that one in particular is
    logging RESET's in its counter display under HUBwatch. They have
    replaced this card with a MCS spare, and since then the LAT diconnects
    have stopped, and the LAVc has stayed operational. However they have
    noticed that the new card has logged 1 reset in 48hrs of uptime. They
    have asked me what the reset actually means - hence this note, and I
    dont know - I can guess, but can anyone tell me what the correct
    definition is/what causes it please?.
    
    I have asked the customer to see if there is an errorlog entry
    available to examine to find more info (from an earlier note) - if he
    finds anything I'll post it.
    
    Thanks again,
    
    joe
    (Product Sales)

T.R Title User Personal
Name Date Lines

1395.1 resets defined NACAD::PAGLIARO Rich Pagliaro, Hub Products Group Fri Sep 09 1994 14:33 28

T.R	Title	User	Personal Name	Date	Lines
1395.1	resets defined	NACAD::PAGLIARO	Rich Pagliaro, Hub Products Group	`Fri Sep 09 1994 14:33`	28
	The total number of resets is reported from one of the repeater's setup port menu options and HUBwatch's Agent Summary view. In both cases, the total resets counter is a summation of three counters: 1. pcomEsysPowerUps - the number of times the device was powered on. 2. pcomEsysMgmtResets - the number of times the device was initialized with a management command (that is, reset with a factory defaults or reset with saved settings). 3. pcomEsysUnsolicitedResets - the number of times the device initialized itself after encountering a fatal error (i.e. crashed). Only "unsolicited resets" cause entries to be added to the error log. When getting this information from HUBwatch, please make sure that the customer is looking at the repeater's agent summary view and not the hub manager's agent summary view. Do please post any error log entries here. Also please post the DECrepeater 900FP's firmware version number. Do the DECrepeater 900FP's have their own IP addresses? Regards, Rich

    The total number of resets is reported from one of the repeater's setup
    port menu options and HUBwatch's Agent Summary view. In both cases, the
    total resets counter is a summation of three counters:

    	1. pcomEsysPowerUps - the number of times the device was powered on.
    
    	2. pcomEsysMgmtResets - the number of times the device was
                                initialized with a management command (that is,
                                reset with a factory  defaults or reset with
                                saved settings).
    
        3. pcomEsysUnsolicitedResets - the number of times the device
                                       initialized itself after
                                       encountering a fatal error (i.e.
                                       crashed).
    
    Only "unsolicited resets" cause entries to be added to the error log.
    When getting this information from HUBwatch, please make sure that the
    customer is looking at the repeater's agent summary view and not the
    hub manager's agent summary view.
    
    Do please post any error log entries here. Also please post the
    DECrepeater 900FP's firmware version number. Do the DECrepeater 900FP's
    have their own IP addresses?
    
    Regards,
    
    Rich