Conference netcad::hub_mgnt

1086.0. "Pb with DECserver900 TM & HUBwatch V3.0 !!" by ZTOIS1::VISTA (Renato VISTA, MCS/SPS France/Strasbourg) Wed Jun 08 1994 10:14

    
    
    Hi,
    
    Working on a DEChub900 (MS version V3.0.0), with DECrepeater900TM
    (1.0G, slot 1) and DECserver900TM (NAS V1.3 BL80-27, slot 3), 
    I've met the following problem :
    
    . using HUBwatch V3.0, executing...
    
    	$WATCH/AGENT /IP=16.188.48.120
    
    	where 16.188.48.120 is INband IP address of DEChub, 
    
    	I've got, in the Message BOX HUBwatch window, ...
    
    14:36:41.53(I*)  
    14:36:41.66(I*) Power Configuration: 
    14:36:41.81(I*) _______________________________________________ 
    14:36:41.96(I*) Power Slots:	1	2	3	4 
    14:36:42.13(I*) Supplies:         In      In      -       In       
    14:36:42.29(I*) _______________________________________________ 
    
    14:39:28.75(E*) snmp: request has no agent defined (slot= 3) 
    14:39:28.93(E*) Invalid request agent 
    
    	Effectively, double-clicking on DECserver900 icon returns no data 
    	and error message...
    
    . using Community Table Management Option, selecting directly
    DECserver900 module, ALL is OK, ie I've got the expected DECserver900
    data...
    
    . at the DEChub900 console level, using the LOG option, I've got the
    message...
    
    
    	3: Network Access Software V1.3 for DS900TM
    	>>Description: BL80-27 	ROM V5.0-0	LAT V5.1	Load Image:W
    	Health-Text:
    	Status:	nonFatalFailure
    
    	...after an INIT DELAY 0 on the DS900TM remote console.
    
    	Please note that the last time I've had this kind of problem was
    	when the external-card software version was not correct (is the
    	DS900 was seen as a DS700 by the previous NAS version...).
    
    
    Is this a known problem ??
    Is this due to the BL80-27 version ??? (In TERMINAL_SERVERS 1746.* item,
    the BL80-29 of NAS V1.3, required as the minimum version by DEChub900
    V3.0.0 & HUBwatch 3.0, does not exist... By the way, the release notes
    are talking about NAS 3.1 BL80-29 for DECserver 900TM... Is this a
    mistake ?)
    
    Thank you for your help.
    Renato
    
        
    	
    
    
    
    

You must have an IP address in the DECserver 900TM, and SNMP must be enabled
in the DECserver 900TM.  Furthermore, its community must be PUBLIC.

From your symptoms, one of these conditions might not be right.

Tom Hood
HUBwatch

    
    Tom,
    
    Thank you for your suggestions.
    
    Here under the DECserver SNMP definition :
    
    SNMP State:                ENABLED      Authentication Failure:   
    ENABLED
    
    
    Community Name                    Address          GET GETNEXT SET TRAP
    
    PUBLIC                            16.188.48.9      ENA  ENA    ENA  ENA
    
    
    Local>
    
    As I've description in .0, the problem doesn't occurs when HUBwatch is
    invoking the DECserver itself directly, or selecting the DECserver via
    Community Table Management OPTION...
    Please also note the NAS V1.3 BL80-27 version of DS900 TM was running
    correctly with the previous DEChub 900 MS V2.1.1 version (ie NO error
    was occurring after DOWNline LOADING of WWENG2.SYS image onto DS900
    TM).
    
    Any other suggestions ?
    
    Renato
    
    

	Hi, I have done a lot of testing on the DS900TM & DS90M. What I found
	then was that the only cummunity setup in the DECserver that worked
	was PUBLIC and ANY address. For that reason I didn't enable set.
	But you should be able to get traps if you specify a second community
	with address 16.188.48.9 and traps enable.

	/Stefan