| 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 |
I have set up two alarm for a remote node (hgsw03) on CIRCUIT DOWN CIRCUIT FAULT
and CIRCUIT UP. But I cannot always detect the events.
I tried GETEVENT NODE4 HGSW03 CIRCUIT SVA-0 CIRCUIT down circuit fault
or GETEVENT NODE4 HGSW03 CIRCUIT SVA-0 CIRCUIT UP, but no response.
Are my rule expression incorrect? Also is there a better way to detect
Circuit UP and DOWN?
Following are the rules expression.
/Susan
Domain SCHWEP_NS:.hkgact Rule hgsw03_circuit_down
AT 25-MAY-1992 18:35:36 Characteristics
Examination of attributes shows:
Alarm Fired Procedure = DKA200:[MCC]MCC_ALARMS_MAIL_ALARM.COM;
2
Description = "REMOTE NODE CIRCUIT DOWN EVENT
OCCURRED"
Batch Queue = "ALARMS$BATCH"
Alarm Fired Parameters = "SCHWEP::DEMO"
Expression = (OCCURS(NODE4 hgsw03 circuit sva-0
CIRCUIT DOWN CIRCUIT FAULT))
Severity = Critical
Domain SCHWEP_NS:.hkgact Rule hgsw03_circuit_up
AT 25-MAY-1992 18:35:15 Characteristics
Examination of attributes shows:
Alarm Fired Procedure = DKA200:[MCC]MCC_ALARMS_MAIL_ALARM.COM;
2
Description = "REMOTE NODE CIRCUIT up EVENT
OCCURRED"
Batch Queue = "ALARMS$BATCH"
Alarm Fired Parameters = "SCHWEP::DEMO"
Expression = (OCCURS(NODE4 hgsw03 circuit sva-0
CIRCUIT up))
Severity = Clear
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3074.1 | cannot detect circuit down until is up!!! | HKGACT::SUSANCHAN | Tue May 26 1992 07:13 | 30 | |
It seems that circuit down circuit fault event cannot be sink out when
NCP> set cir sva-0 state off.
Please see the OPCOM message below which is extracted from the operator.log
on the DECmcc system.
??? Is there a better way to detect circuit down ???
Thanks,
Susan
%%%%%%%%%%% OPCOM 26-MAY-1992 16:44:10.20 %%%%%%%%%%% <======== See the
Message from user DECNET time
DECnet event 4.7, circuit down, circuit fault difference
From node 22.1010 (HGSW03), 26-MAY-1992 14:08:49.77 <========
Circuit SVA-0, Line synchronization lost
%%%%%%%%%%% OPCOM 26-MAY-1992 16:44:10.22 %%%%%%%%%%%
Message from user DECNET
DECnet event 4.10, circuit up
From node 22.1010 (HGSW03), 26-MAY-1992 16:37:40.64 <======== circuit
Circuit SVA-0 didn't set
to up until
%%%%%%%%%%% OPCOM 26-MAY-1992 16:44:10.26 %%%%%%%%%%% then
Message from user DECNET
DECnet event 4.15, adjacency up
From node 22.1010 (HGSW03), 26-MAY-1992 16:37:40.72
Circuit SVA-0, Adjacent node = 22.709 (HGODR1)
| |||||
| 3074.2 | set LINE off for testing | ICS::WOODCOCK | Tue May 26 1992 10:15 | 14 | |
>It seems that circuit down circuit fault event cannot be sink out when >NCP> set cir sva-0 state off. Whenever I am 'testing' for events I shut off the *LINE* but leave the CIRCUIT up. This creates the circuit down circuit fault event at least for sync circuits (never tried it for ethernet) NCP> set line sva-0 state off regards, brad... | |||||
| 3074.3 | see if this helps!!! | KITFOX::BALL | Tue May 26 1992 13:37 | 35 | |
( 1 ) the rules seem correct...
( 2 ) i usually alarm off of circuit down event 4.8 and circuit up event 4.10...
( 3 ) you said you don't receive either event...
is your filter set up up correctly to receive these events???
MCC> show node4 hgsw03 outbound stream stream_for_events remote sink -
monitor all cha
we are looking specifically for events 4.8 Circuit down and
4.10 Circuit up
( 4 ) is the sink up and running???
( 5 ) is their a mcc_dna4_evl process on your system???
$ show system
( 6 ) if all of this is true start out with simple testing
MCC> getevent node4 hgsw03 circuit sva-0 circuit up
---> other window <---
MCC> disable node4 hgsw03 circuit sva-0 ! turn the circuit state off
MCC> enable node4 hgsw03 circuit sva-0 ! turn the circuit state on
MCC> getevent node4 hgsw03 circuit sva-0 circuit down
---> other window <---
MCC> disable node4 hgsw03 circuit sva-0 ! turn the circuit state off
MCC> enable node4 hgsw03 circuit sva-0 ! turn the circuit state on
( 7 ) if this works now try your alarms again...
( 8 ) if it does not work contact me and we'll get you going...
phone number: 226-5345
enet address: took::d_ball
- darryl
| |||||
| 3074.4 | How to detect circuit down by event?! | HKGACT::SUSANCHAN | Wed May 27 1992 01:36 | 52 | |
First of all, the environment for trapping DECnet event is setup correctly.
I tested it be the ZERO COUNTER DECnet event, and I got what I expected.
I want to verify that CIRCUIT DOWN CIRCUIT FAULT 4.7 is the DECnet event I
should detect when NCP> SET CIR SVA-0 STATE OFF.
Second,
MCC> disable node4 hgsw03 circuit sva-0 ! turn the circuit state off
MCC> enable node4 hgsw03 circuit sva-0 ! turn the circuit state on
the second command cannot be performed since the circuit is off no connection
can be made.
Third,
MCC> getevent node4 hgsw03 circuit sva-0 circuit up
MCC> enable node4 hgsw03 circuit sva-0 ! turn the circuit state on
MCC> getevent node4 hgsw03 circuit sva-0 circuit down
MCC> disable node4 hgsw03 circuit sva-0 ! turn the circuit state off
give no response/output.
Fourth, I believe I have verify that the when I do
NCP> SET CIR SVA-0 STATE OFF
only the console will be able to receive the message but not the sink nodes.
Also if the cir state off for a period of time the CIRCUIT DOWN CIRCUIT FAULT
opcom message is lost. Only the CIRCUIT UP opcom message will be received
when I do
NCP> SET CIR SVA-0 STATE ON
QUESTION:
Any suggestion on detecting circuit down using event?
Thanks,
Susan Chan
HKEIS (hong kong)
| |||||