[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

2881.0. "global wildcard alarm excep: where is entity??" by ICS::WOODCOCK () Wed Apr 29 1992 18:13

Hi there,

Using a global wildcard in an alarm, how do you tell what the entity which
failed the poll in the exception handler is? In the example below I show the
8 parameters being passed and type the file name given. I can't tell what node
is DOWN!!! Guess where this leaves me.

help appreciated,

rock->  brad  <-hard_place

ps. the node4 down is LHPK02 and it shows up as the ENTITY in the notification
window

--------------------------------------------------------------------------
Current queue:    MCC$BATCH
  P1 = "MCC 0 ALARMS RULE poll_pko-24"
  P2 = ""
  P3 = ""
  P4 = "(node4 * circuit * substate <> none,at every 0:30:0"
  P5 = "29-APR-1992 14:05:40.33"
  P6 = "Node not currently accessible."
  P7 = ""
  P8 = "SYS$SCRATCH:MCC_ALARMS_DATA_14054033.DAT"
RULE: MCC 0 ALARMS RULE poll_pko-24
DESCRIPTION:
CATEGORY:
EXPRESSION: (node4 * circuit * substate <> none,at every 0:30:0)
TIME: 29-APR-1992 14:05:40.33
EVIDENCE: Node not currently accessible.
EVENT_ARGUMENTS:
PARAMETER:
SEVERITY: Indeterminate                                                        
DOMAIN: Domain LUVBOT_NS:.PKO-24

T.RTitleUserPersonal
Name
DateLines
2881.1The last 5% is always the hardest 8(MOLAR::ROBERTSKeith Roberts - DECmcc Toolkit TeamThu Apr 30 1992 12:2515
RE: .0

> Using a global wildcard in an alarm, how do you tell what the entity which
> failed the poll in the exception handler is? In the example below I show the
> 8 parameters being passed and type the file name given. I can't tell what node
> is DOWN!!!

  Sorry about that Brad .. guess this little detail got left out of the
  phase-0 document  .. 8)

  The Entity information has been omitted!  I'll enter a QAR on Alarms 

	QAR # 2848

  /keith
2881.2waiting for fix :-)ICS::WOODCOCKThu Apr 30 1992 13:1030
>  Sorry about that Brad .. guess this little detail got left out of the
>  phase-0 document  .. 8)

>  The Entity information has been omitted!  I'll enter a QAR on Alarms 

>	QAR # 2848

  Hi keith,

Ouch, that hurt. Thanks for the QAR. As an aside though I've been using the
global wildcard for at least a week now. It has been working *outstanding*.
I used to have 60 rules (one for each router) and the scheduling of the
polling seemed to cause occasional problems (read: internal error with decnet
phase_iv am exceptions). This appears to have been greatly reduced.

I have now changed the entire map structure to accommadate these rules. I've
got one rule for every lower level domain polling all node4 entities. I have
taken out any duplicate entities within the lower structure. Before, if a 
router within a domain had a connection to another domain then both routers
were placed in both domains. In each domain the 'second' router has been
removed and a simple text reference has been added.

I now have twelve rules polling all routers and even the load hosts (but you
gotta fix the above prob for it to work completely). In any event, the batch
job restarts each night. Polling new routers becomes a simple IMPM add of the
router to the domain. Woooooeeeeee, alarm change mngmt at its best. **NONE**

a much needed, much much appreciated feature,
brad...

2881.3We're happy .. if you're happy 8)MOLAR::ROBERTSKeith Roberts - DECmcc Toolkit TeamThu Apr 30 1992 15:3312
  Brad .. I'm glad you find Alarm Global Wildcards to be so useful.

  It was a last minute decision to squeeze the functionality into v1.2,
  but from what you have indicated .. it was the 'right thing to do'.

  As you have already noticed, the Global Wildcards are dynamic, in that
  Alarms senses changes to the domain; polling new entities as they are
  added.  This increases the communication with the Domain FM .. but the
  alternative would be to disable & enable a rule whenever you modified
  the domain membership .. yuck ..

  /keith
2881.4good stuff, even if it's lateICS::WOODCOCKThu Apr 30 1992 16:2613
Keith,

>  As you have already noticed, the Global Wildcards are dynamic, in that
>  Alarms senses changes to the domain; polling new entities as they are
>  added.  This increases the communication with the Domain FM .. but the
>  alternative would be to disable & enable a rule whenever you modified
>  the domain membership .. yuck ..

I actually hadn't noticed that it was dynamic. I figured it wasn't going to
pick it up until the batch job recycled at midnight. 

most impressive,
brad...
2881.5fixedCTHQ3::WOODCOCKMon Jul 20 1992 19:224
As a follow up the SSB kit now gives the NODE under the MANAGED OBJECT field.

thanks,
brad...
2881.6just a little bit more info... maybe?CX3PT3::SHOTO::W_MCGAWFri Sep 18 1992 19:1013
    Hi,
    
    I don't mean to sound unappreciative... but I have a customer who
    thinks we need to go one step better and provide the NAME of the node
    instead of the address in the MANAGED OBJECT field.  He has operators
    that get notified by the wildcard alarm rule and DECnet addresses are
    meaning less to them.  Is there any chance that the synonym name could
    be included as well as the address?
    
    Any other suggestions would would be welcome.
    
    Thanks'
    Walt
2881.7SYNONYM instead of ADDRESS is a MUSTCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentSun Sep 20 1992 03:0811
    My customer paid for a custom tool to be written, layered on top of
    RBMS, to be able to accomplish just what you want.  Until DECmcc ELM_AM
    is able to accomplish the same thing, my customer will keep this custom
    tool around.  Not good.  
    
    This is a MUCH NEEDED and CUSTOMER-REQUIRED capability.  Expect to have
    more customers ask for, and even demand, this.
    
    You guys would be my heroes if you did it.
    
    -Dan