| $! MCC_ALARMS_SAMPLE_RULES.COM, Version: X01.10-00
$!
$!
$! **************************************************************
$! * ********************************************************** *
$! * * * *
$! * * Copyright (c) Digital Equipment Corporation, 1990 * *
$! * * All Rights Reserved. Unpublished rights reserved * *
$! * * under the copyright laws of the United States. * *
$! * * * *
$! * * The software contained on this media is proprietary * *
$! * * to and embodies the confidential technology of * *
$! * * Digital Equipment Corporation. Possession, use, * *
$! * * duplication or dissemination of the software and * *
$! * * media is authorized only pursuant to a valid written * *
$! * * license from Digital Equipment Corporation. * *
$! * * * *
$! * * RESTRICTED RIGHTS LEGEND Use, duplication, or * *
$! * * disclosure by the U.S. Government is subject to * *
$! * * restrictions as set forth in Subparagraph (c)(1)(ii) * *
$! * * of DFARS 252.227-7013, or in FAR 52.227-19, as * *
$! * * applicable. * *
$! * * * *
$! * ********************************************************** *
$! **************************************************************
$!
$!
$! Edit history:
$! ------------
$! 14-Jun-1990 X01.00-001 JP Created
$! 25-Jun-1990 X01.00-002 JP Added more rules
$! 20-FEB-1991 X01.10-000 AVN Added more rules
$!
$! Description:
$!
$! This file contains sample alarm rules that can be modified for use with
$! the DECmcc Alarms package in a particular network environment.
$!
$! It is suggested that the sample rules given here be cut out of this file
$! with an editor and inserted into a separate command procedure before
$! the rules are edited for a particular network environment.
$!
$ MANAGE/ENTERPRISE
!
! *****************************************************************************
! DECNET PHASE IV alarm rules...
! *****************************************************************************
!
! =: Circuit Problem :=
!
CREATE MCC 0 ALARMS RULE CIRCUIT_SUBSTATE -
EXPRESSION = (CHANGE_OF(NODE4 dummy CIRCUIT una-0 SUBSTATE, NONE, *)) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_MAIL_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_MAIL_EXCEPTION.COM ,-
CATEGORY = "Circuit problems" ,-
DESCRIPTION = "If the substate is anything other than NONE, then -
either there is a problem with the circuit or the -
circuit is in the OFF or SERVICE state." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "NETWRK::MANAGER"
!
! =: Node unreachable :=
!
CREATE MCC 0 ALARMS RULE REMOTE_NODE_STATE -
EXPRESSION = (NODE4 dummy REMOTE NODE rnode STATE = UNREACHABLE ,-
AT EVERY 00:30:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_MAIL_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_MAIL_EXCEPTION.COM ,-
CATEGORY = "Node unreachable" ,-
DESCRIPTION = "If a node becomes unreachable, the alarm notification -
command procedure will be run. If there is a -
communication failure, the exception handler will be -
executed. Use this rule to ensure that crucial nodes -
are reachable from a particular routing node. To be -
useful, the NODE4 is a router in the same area as the -
remote node." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "NETWRK::MANAGER"
!
! =: Area unreacahble :=
!
CREATE MCC 0 ALARMS RULE REMOTE_AREA_STATE -
EXPRESSION = (NODE4 dummy AREA 1 STATE = UNREACHABLE ,-
AT EVERY 00:30:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_BROADCAST_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_BROADCAST_EXCEPTION.COM ,-
CATEGORY = "Area unreachable" ,-
DESCRIPTION = "If an area becomes unreachable, the alarm notification -
command procedure will be run. If there is a -
communication failure the exception handler will be -
executed. Use this rule to ensure that crucial areas -
are reachable from a particular area routing node. -
To be useful, the NODE4 should be an area router, as -
other nodes do not know about other areas." ,-
QUEUE = "ALARMS$BATCH",-
PARAMETER = "USER=NETMANAGER"
!
! =: Transmit problems :=
!
CREATE MCC 0 ALARMS RULE LINE_CONTENTION -
EXPRESSION = (CHANGE_OF(NODE4 dummy LINE qna-0 SEND FAILURE,*, *) ,-
AT EVERY 00:10:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_BROADCAST_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_BROADCAST_EXCEPTION.COM ,-
CATEGORY = "Transmit problems" ,-
DESCRIPTION = "If a line cannot send a packet after 16 attempts this -
counter will increase. This is only true for ethernet -
lines and usually indicates that the channel is very -
heavily used." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "USER=NETMANAGER"
!
! =: Trafic Indicator :=
!
CREATE MCC 0 ALARMS RULE PEAK_LINKS -
EXPRESSION = (NODE4 dummy MAXIMUM LOGICAL LINKS ACTIVE>30 ,-
AT EVERY 12:00:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_LOG_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_LOG_EXCEPTION.COM ,-
CATEGORY = "Traffic Indicator" ,-
DESCRIPTION = "This attribute represents the peak number of logical -
links active on the specified system. If this counter -
regularly reaches the value of MAXIMUM LINKS, some -
users may be experiencing network resource problems. -
Set the constant value (30 above) to or near your -
MAXIMUM LINKS value." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "NODE_ALARMS.LOG"
!
! =: Configuration problem :=
!
CREATE MCC 0 ALARMS RULE PIPELINE_QUOTA -
EXPRESSION = (NODE4 dummy PIPELINE QUOTA < 10000, AT EVERY 12:00:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_LOG_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_LOG_EXCEPTION.COM ,-
CATEGORY = "Configuration problem" ,-
DESCRIPTION = "The minimum value suggested for this characteristic is -
recommended to be 10000. If the pipeline quota is less -
that 10000 communication throughput will be decreased.",-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "NODE_ALARMS.LOG"
!
! =: Configuration problem :=
!
CREATE MCC 0 ALARMS RULE BAD_TYPE -
EXPRESSION = (NODE4 dummy TYPE <> EndNodeIV, AT EVERY 12:00:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_LOG_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_LOG_EXCEPTION.COM ,-
CATEGORY = "Configuration problem" ,-
DESCRIPTION = "This checks to ensure that end nodes do not -
inadvertently become routing nodes. This can cause -
*MAJOR* problems in your network." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "NODE_ALARMS.LOG"
!
!
! *****************************************************************************
! BRIDGE alarm rules...
! *****************************************************************************
!
CREATE MCC 0 ALARMS RULE BRIDGE_BROKEN -
EXPRESSION = (BRIDGE dummy DEVICE STATE <> OPERATING ,-
AT EVERY 00:15:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_MAIL_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_MAIL_EXCEPTION.COM ,-
CATEGORY = "Configuration problem" ,-
DESCRIPTION = "The bridge is either broken or initializing. If the -
bridge cannot be reached (communication problems), -
the exception handler procedure will be executed. -
Check the DEVICE BROKEN REASON attribute of the bridge -
for more information." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "NETWRK::MANAGER"
!
!
!
CREATE MCC 0 ALARMS RULE BRIDGE_IS_LISTENER -
EXPRESSION = (BRIDGE dummy BRIDGE FUNCTION <> BRIDGE ,-
AT EVERY 00:15:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_MAIL_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_MAIL_EXCEPTION.COM ,-
CATEGORY = "Configuration problem" ,-
DESCRIPTION = "The bridge is currently operating as a LTM listener. _
Use this rule for bridges in your local area network _
whose availability is crucial." ,-
QUEUE = "ALARMS$BATCH" -
PARAMETER = "NETWRK::MANAGER"
!
!
!
CREATE MCC 0 ALARMS RULE SPANNING_TREE_CHANGE -
EXPRESSION = (CHANGE_OF(BRIDGE dummy SPANNING TREE MODE CHANGES,*, *),-
AT EVERY 00:10:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_BROADCAST_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_BROADCAST_EXCEPTION.COM ,-
CATEGORY = "Configuration problem" ,-
DESCRIPTION = "Either a LANbridge 100 bridge has been added or -
removed from your local area network. The bridge -
specified must be either a LANbridge 150 or 200." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "USER=NETMANAGER"
!
! =: Bridge Reset problem :=
!
CREATE MCC 0 ALARMS RULE BRIDGE_RESETS -
EXPRESSION = (CHANGE_OF(BRIDGE dummy UNSOLICITED RESETS, *, *) ,-
AT EVERY 00:15:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_BROADCAST_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_BROADCAST_EXCEPTION.COM ,-
CATEGORY = "Bridge Reset problem" ,-
DESCRIPTION = "Whenever a LANbridge 150 or 200 encounters a serious -
internal problem it will reset itself. This may be -
caused by power glitches and/or deteriorating hardware. -
It this problem occurs frequently field service may -
need to be informed." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "USER=NETMANAGER"
!
! =: Bridge Problems :=
!
CREATE MCC 0 ALARMS RULE BRIDGE_LINE_DISABLED -
EXPRESSION = (BRIDGE dummy LINE 1 PORT MODULE STATE <> FORWARDING ,-
AT EVERY 00:15:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_LOG_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_LOG_EXCEPTION.COM ,-
CATEGORY = "Bridge problem" ,-
DESCRIPTION = "The line is not operating properly. It may have been -
disabled by a management directive, or it might be -
broken. Use this rule for lines in your local area -
network whose availability is crucial." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "NODE_ALARMS.LOG"
!
! =: Transmit problems :=
!
CREATE MCC 0 ALARMS RULE LINE_COLLISIONS -
EXPRESSION = (CHANGE_OF(BRIDGE X LINE 1 COLLISION LIMIT EXCEEDED,*,*),-
AT EVERY 00:10:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_LOG_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_LOG_EXCEPTION.COM ,-
CATEGORY = "Transmit problems" ,-
DESCRIPTION = "If a line cannot send a packet after 16 attempts this -
counter will increase. This is only true for lines on -
a LAN Bridge 200, and usually indicates that the line -
is very heavily used." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "NODE_ALARMS.LOG"
!
! =: BRIDGE memory problem :=
!
CREATE MCC 0 ALARMS RULE BRIDGE_MEMORY_BAD -
EXPRESSION = (BRIDGE dummy NVRAM FAILED FLAG = TRUE ,-
AT EVERY 12:00:00) ,-
PROCEDURE = MCC_COMMON:MCC_ALARMS_LOG_ALARM.COM ,-
EXCEPTION HANDLER = MCC_COMMON:MCC_ALARMS_LOG_EXCEPTION.COM ,-
CATEGORY = "BRIDGE memory problem" ,-
DESCRIPTION = "If there is a problem with the memory in the specified -
bridge this rule will fire. Field service should be -
notified." ,-
QUEUE = "ALARMS$BATCH" ,-
PARAMETER = "NODE_ALARMS.LOG"
!
!
!=======================================================================================
!
EXIT
$ EXIT
|