[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

3459.0. "MAM 4.1.1 Warning Yellow Cond not sensed!" by ZUR01::ACKERMANN () Tue Apr 16 1996 16:10

    
    
    
    
        Hello all,
    
        Problem: Hubwatch V4.1.2 Hub900 with MAM V4.1.1 does not recognize
                 Yellow Temp condition in Chassis Environmental Summary.
    
        In the LCD Display of the MAM Module it shows Warning "Yellow Temp
        Condition" from about 65C. From about 75C it shows "Red Temp Condition"
        In Hubwatch it reports only the "Red Temp Condition" but no Yellow
    	Condition. 
    
        So what we did: we looked in to the DECHUB900 "Chassis MIB",
        there You can see that 3 states of the Sensor are possible:
        Good, warning and bad.
        Now, we looked with the MIB Browser of Netview in to the actual Sensor
        state and it reported only two states: Good or bad!
    
        Below the printout of the Normal Condition:
        Name or IP Address: 16.XX.XX.XX
    
        Community Name: public
    
        MIB Object ID:
        .iso.org.dod.internet.private.enterprises.dec.ema.mib-extensions-
        1.decHub900.mgmtAgent.mgmtAgentVersion1.chassis.chasEnviron.
        chasEnvironTable.chasEnvironEntry
    
        MIB Instance:
    
        SNMP Set Value:
    
        MIB Value:
                3.1 : good
                3.2 : good
                3.3 : good
                6.1 : good
                6.2 : good
                6.3 : good
                9.1 : good = MAM Slot 9 Sensor 1 status Good or bad!
    
        So that means, that the MAM never sends a warning Condition(Yellow)
        which can be identified by Hubwatch or a MIB-Browser.
        We tried also with Hubwatch 4.1.1 and MAM 4.1.0 bevore.
        So, is these a known Bug or Problem, which will be fixed in a future
        Release of the MAM Code ?
    
        Thanks for any Help,
    
        Daniel MCS Switzerland
    
    
    
T.RTitleUserPersonal
Name
DateLines
3459.1new to usNETCAD::MILLBRANDTanswer mamWed Apr 17 1996 13:379
Hi,

This wasn't a known problem until you brought it up!
The MAM team will look into fixing the mib object.

How did you happen to be testing this?  Zap your
hub with a shrink-wrap gun?  This could be fun.

	Dotsie
3459.2"Heating just with a Hair dryer.."ZUR01::ACKERMANNWed Apr 17 1996 15:0224
    
    
    
    Hi Dotsie,
    
    Thanks for Your Quick Response. 
    
    <<How did you happen to be testing This? Zap your
    hub with a shrink-wrap gun? This could be fun.>>
    
    Not with a "shrink-wrap gun" but with a Hot-Air-Blower
    (Hair Dryer) to the Temp sensor LM34D!
    
    Thanks, for Your offer to look in to it, and to try
    to fix the MIB object.
    But i think, better open up an IPMT, because these
    happens on a Customer Base and he wants to have a
    Solution for these Problem. 
    
    Thanks,
    
    Daniel 
    
    
3459.3Fixed in next releaseNETRIX::&quot;boyle@dechub.lkg.dec.com&quot;Chip BoyleFri Apr 19 1996 20:187
Daniel,
The problem has been fixed, and will be in the next firmware release
for the DEChub 900.

Regards,
Chip
[Posted by WWW Notes gateway]
3459.4<Thanks>ZUR01::ACKERMANNMon Apr 22 1996 08:106
    
    Hi Chip,
    
    Thanks for Your fast help,  
    
    Daniel MCS Switzerland