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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

6024.0. "NO alarm from CHIPCOM MIB CHILD ENTITY" by SALUD::ORTIZ () Fri Jun 17 1994 17:54

    I have a support engineer that is not able to get an alarm to work for
    a Chipcom device. The device is a Chipcom Basic Ethernet Mgt. Module
    (5101M-MGT) v3.2-B. 
    
    He uses the following hub alarm:
    
    DELETE domain .chipcom_hubs rule SMIBAS01_PRIMARY_POWER_FAILURE
    create domain .chipcom_hubs rule SMIBAS01_PRIMARY_POWER_FAILURE -
    expression = (SNMP SMIBAS01 CHIPCOM CHIPMIB02 chipProducts ONLINE olENV
    -
    OLENVPSTABLE 1 olEnvPSOperStatus <> active, at every 00:02:00), -
    description = "SMIBAS01 **PRIMARY POWER FAILURE**" ,-
    severity = WARNING ,-
    batch queue = mcc$alarm ,-
     ALARM FIRED PROCEDURE     = DKA0:[MCC_COMMON.ALARMS]HUB_NOPWR_MAIL.COM   
    ,-
     ALARM EXCEPTION PROCEDURE = MCC_COMMON:MCC_ALARMS_MAIL_EXCEPTION.COM
    ,-
     ALARM FIRED PARAMETER     = "[DECMCC]MCC_ALARMS.TXT"
    
    
    He is able to do a show on the olEnvPSOperStatus, but is not able to
    get the alarm to work. He installed the follow CHIPCOM MIB (only parts
    of it that may be relevant) to do his MCC V1.3 product:
    
    Version     Description
    ------------------------------------------------------------------
    --   v1.0      Initial version of the chipmib02 branch.
    --   v2.0      Version tracking initiated.
    --   v2.1      Version release with TRMM v.2.10
    --
    --
    
    --
    -- Agents supporting this MIB:
    --      Ethernet Management Module, Software rev: v3.2
    --      Ethernet to Ethernet Bridge Module, Software Rev: v2.12
    --      Ethernet to Ethernet Bridge Box, Software Rev: v2.12
    --      Token Ring Management Module, Software Rev: v2.1
    --      Ethernet Interconnect Module, Software Rev: v1.0
    --
    
    -
    -- ONline Groups
    --
    
    olAgents        OBJECT IDENTIFIER ::= { online   1 }
    olConc          OBJECT IDENTIFIER ::= { online   2 }
    olEnv           OBJECT IDENTIFIER ::= { online   3 }
    olModules       OBJECT IDENTIFIER ::= { online   4 }
    olNets          OBJECT IDENTIFIER ::= { online   5 }
    olGroups        OBJECT IDENTIFIER ::= { online   6 }
    olAlarm         OBJECT IDENTIFIER ::= { online   7 }
    
    
    
    olEnvPSOperStatus OBJECT-TYPE
            SYNTAX INTEGER {
                    active(1),
                    standby(2),
                    faulty(3),
                    not-installed(4)
                    }
            ACCESS read-only
            STATUS mandatory
            DESCRIPTION
                    "The current operational state of the power supply.  A
    power
                    supply in standby does not provide power to the
    concentrator."
            ::= { olEnvPSEntry 3 }
    
    
    
    Is there something I am missing here as why he cannot alarm on 
    olEnvPSOperStatus? We have to CHIPCOM and they believe that since it
    compiled and he can do a SHOW on the child entity that it should work.
    
    
    I really need some help on this one...
    
    Thanks,
    Richard 
    
    
    
T.RTitleUserPersonal
Name
DateLines
6024.1What's the result of a show?NYOSS1::PLUNKETTFri Jun 17 1994 20:266
    What's the values he gets back when he does a show?
    
    Can or have you induced a primary power supply failure, done a show,
    and examined the result?
    
    -Craig
6024.2VALUE = FAULTYSALUD::ORTIZWed Jun 22 1994 18:1610
    Sorry it took so long, but I was on vacation...
    
    The answer to your question for value when doing a SHOW was the value
    FAULTY. I wasn't able to get of the customer, but I believe he did
    say they can induce the primary power supply failure. I will check
    on this...
    
    Thanks for replyin...
    
    Richard
6024.3Yes, he can induce power supply failureSALUD::ORTIZThu Jun 23 1994 15:348
    I talked to the customer and he can induce the primary power supply
    failure. When he does the show a FAULTY value is seen..
    
    Hope this helps. Thanks again for the response Craig. If you have
    anymore input, please do so...
    
    Richard
    
6024.4I should have asked this in the first replyNYOSS1::PLUNKETTFri Jun 24 1994 11:445
    So has he performed the experiment where the primary power supply was
    left off line for 3 minutes or so, to guarantee that the both the rule
    would be evaluated and the value "faulty" returned by the poll?  
    
    -Craig
6024.5good question..will find out answerSALUD::ORTIZFri Jun 24 1994 16:158
    Craig,
    
    	That is a good question. I will check on this and get back to
    you...
    
    Thanks,
    Richard
    
6024.6waits over 5 minutes SALUD::ORTIZThu Jun 30 1994 15:1415
    From:   31534::TEERLINK
    To:     SALUD::ORTIZ
    CC:
    Subj:   MCC use of rules for more than 5 min.
    
    Richard,
    
    The answer is yes.  It is infact running all the time (it gets loaded
    at boot along with the rules for IP reachability.)
    
    Dave
       
    
    
    Any other ideas would be appreciated....
6024.7We can almost say that there's a problem, but not yetNYOSS1::PLUNKETTFri Jul 01 1994 04:0323
    Well, that's close to the answer that I was looking for.  What I
    want to know is not just if the rule has been running for more than
    five minutes, what I want is also to find out for sure if the rule
    has been evaluated during the time that the primary power supply was
    definitely disabled.  I forget the fcl syntax to find out the last
    evaluation time of the rule, but in order to determine if the rule
    is not working, we have to somehow set up a situation where we can
    guarantee that the rule's evaluation at a particular time would have
    caused it to fire.
    
    If the reply had been that *both* the rule had been running for more
    than five minutes, and that the primary power supply had been
    disabled for more than five minutes, we could then conclude that
    there was a problem with the mcc enviroment somehow.
    
    Actually, I should restate the previous sentence.  We need to make
    sure that during this rule's evaluation, that the variable being
    tested will return a value that causes the rule to fire.  The
    response that you forwarded doesn't allow me to conclude that what
    we're looking for actually happened.  Whoever sent it, left out
    information about the state of the power supply.
    
    -Craig