[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

4883.0. "Need help writing rules." by GRANPA::JUWEBB () Wed Apr 14 1993 15:52

    Hi,
    
    I'm working on a project at a customer site and we are using DECmcc
    to manage the network.  We are in the design phase and I need to 
    write rules to monitor these network elements:
    			router - DEC WANrouter 250, DECnis 500
    			bridge - LANBridge 150
    			X.25 gateway
    			DECrepeater 90C
    			DECserver 250.
    
    Can anyone help me get started writing rules?  We don't have the
    network set up to test the equipment or check for events.
    
    Thanks,
    
    Juanita

T.R Title User Personal
Name Date Lines

4883.1 USE FCL as first step in writing alarm rules CUJO::HILL Dan Hill-Net.Mgt.-Customer Resident Wed Apr 14 1993 17:39 42

T.R	Title	User	Personal Name	Date	Lines
4883.1	USE FCL as first step in writing alarm rules	CUJO::HILL	Dan Hill-Net.Mgt.-Customer Resident	`Wed Apr 14 1993 17:39`	42
	Hi, Juanita, A simple way to get used to alarms syntax involves the use of Forms Command Line PM. $mana/enter MCC> use mode form Now spend some time learning this interface. Look specifically at the use of the PF2 key, the F17 key, and the SELECT key. When you type in a command, be sure the VERB is on the VERB line and the ENTITY is on the ENTITY line. Example: Verb: SHOW Entity: NODE .decnis500 ^ \| At this point, press PF2. Next press F17. Next use the arrow keys to move to the desired child entity, then press SELECT. Keep repeating this to work your way down the entity hierarcy. Use the Arguments and Qualifiers fields in the same way. Substitues wild cards for multiple entities. Select individual attributes of interest. The syntax you use for looking at an entity's attributes is the same syntax you will use in the EXPRESSION of an alarm rule. Note that when you write an alarm rule, you need only supply an alarm name, expression, domain, and perceived severity. You can get fancy with logging and alarms fired procedures later. Make your first alarm rules simple. They will also cost you less in terms of overhead. -Dan

    Hi, Juanita,
    
    A simple way to get used to alarms syntax involves the use of Forms
    Command Line PM.
    
    $mana/enter
    MCC> use mode form
    
    Now spend some time learning this interface.  Look specifically at the
    use of the   PF2 key, the F17 key, and the SELECT key.
    
    When you type in a command, be sure the VERB is on the VERB line and
    the ENTITY is on the ENTITY line.
    
    Example:
      Verb:   SHOW
      Entity: NODE .decnis500
                             ^
                             |
                           At this point, press PF2.
                           Next press F17.
                           Next use the arrow keys to move to the desired
                             child entity, then press SELECT.  
                           Keep repeating this to work your way down the
                             entity hierarcy.
    
     Use the Arguments and Qualifiers fields in the same way.
     Substitues wild cards for multiple entities.
    
    Select individual attributes of interest.  
    
    The syntax you use for looking at an entity's attributes is the same
    syntax you will use in the EXPRESSION of an alarm rule.
    
    Note that when you write an alarm rule, you need only supply an alarm
    name, expression, domain, and perceived severity.  You can get fancy
    with logging and alarms fired procedures later.
    
    Make your first alarm rules simple.  They will also cost you less in
    terms of overhead.
    
    -Dan