| 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 |
Hello,
We run DECmcc (V1.3) on ULTRIX (4.3a). We use DNS. The DNSserver is a VMS system.
We have the a problem with alarm rules. We do the following:
1.We created an alarm rule for a bridge
MCC> create domain roche:.mcc_kau.bas_bridge -
rule bridge_rb$b_0057_line2_collision_limit_exceeded -
expression = (change_of (bridge roche:.bas.rb$b_0057 line 2
collision limit exceeded, *,*), at every=00:30)
severity = major
2. The rule doesnt work.
MCC> show domain roche:.mcc_kau.bas_bridge Rule
bridge_rb$b_0057_line2_collision_limit_exceeded all status
Domain roche:.mcc_kau.bas_bridge Rule bridge_rb$b_0057_line2_
collision_limit_exceeded
AT 1993-07-07-11:56:38.887 Status
Examination of attributes shows:
State = Enabled
Substate = Running
Time of Last Evaluation = 1993-07-07-11:56:26.477
Result of Last Evaluation = Error
Error Condition = "The entity Bridge LOCAL_NS:.bas.
rb$b_0057 LINE 2 is not registered"
Error Entity = Bridge 0:.bas.rb$b_0057 LINE 2
Current Severity = Indeterminate
You see, The entity we want to check via the rule is "1roche:.bas.rb$b_0057
line 2" but the rule checks the entity "LOCAL_NS:.bas.rb$b_0057 LINE 2". We
work with the namespace "roche" and not "local_ns".
Whats the problem? Is it a bug? Is there a fix for?
Regards Roland
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5373.1 | Alarms is using MIR instead of DNS | TOOK::KWAK | Thu Jul 22 1993 10:06 | 19 | |
Check the logical MCC_DNS_SELECTION.
Make sure that the logical is defined to be DNS.
It may be possible that your Alarm rule was created when the
MCC_DNS_SELECTION was set to MIR.
It may also be possible that the Alarm module running on system
is using MIR instead of DNS.
You can do following:
$ mcc_kill
$ manage
MCC> sho mcc 0 all char
MCC> enroll mcc_alarms_fm
MCC>! create the rule ....
William
| |||||
| 5373.2 | We checked this before | ZUR01::SCHNEIDERR | Fri Jul 23 1993 02:53 | 17 | |
William, Thanks for your answer. This system is runing for some time already. The MCC_DNS_SELECTION is set right. We didin't change it. The customer worked a lot with this machine. There are hunderts of nodes registered, all under DNS. > You can do following: > $ mcc_kill > $ manage > MCC> sho mcc 0 all char > MCC> enroll mcc_alarms_fm > MCC>! create the rule .... We will try to reenroll the alarms_fm, but I think there will be no changes. Regards | |||||
| 5373.3 | Now it works | ZUR01::SCHNEIDERR | Fri Jul 23 1993 11:08 | 9 | |
William, The hint with reenroll the alarm FM was good. We did it and now it works. Now I know more about the history of this system but why we had to reenroll I don't know. This customer had an MCC VMS system with DNS and now he changed to MCC ULTRIX. Maybe something went wrong during the new installation. Now it works....Thanks...Roland | |||||
| 5373.4 | still the same problem | ZUR01::SCHNEIDERR | Wed Jul 28 1993 05:03 | 9 | |
William, Sorry, to say that. We have still the same problem. Reenroll of the alarm_fm didn't help. We saw it now after we made some more investigations. So..still the same problem Roland | |||||