| 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 am testing to see if I can get target notification to work but am running into a problem. (DECmcc V1.2.3) I have done a number of target assigns and deassigns now I have ended up in a situation that when I assign a target I get "Assignment already exists, no changes made." But if I do a MCC>DIRECTORY TARGET DOMAIN * it displays "No matching targeting entry found." for each domain and when I do a dump of MCC_SYSTEM:MCC_TARGET_DATA_MIR.DAT there appears to be a couple of target assignments that I had previously deassigned. Is this a known problem? If so, is there a solution or work around? Basically what I am try to do is get the node icon of the node that I am checking the reachability of instead of the router node icon foe when a specific alarm fires which is: Create domain computer_room rule billc_remote_node_state - expression = (Node4 ndlan remote node billc state = unreachable, - at every 00:02:00) - category = "Node unreachable" - description = "node billc has become unreachable" - alarm fired procedure = mcc_common:mcc_alarms_mail_alarm.com - alarm exception procedure = mcc_common:mcc_alarms_mail_exception.com - alarm fired parameters = "mccsta::mcc" - severity = critical For a sanity check what should my target assignment look like? Another problem which I have not looked into yet is that no mail is received when the alarm fires. Any ideas? Thanks for any assistance, much appreciated.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5306.1 | Re-create the MIRs | TRKWSH::COMFORT | Here beside the rising tide | Thu Jul 08 1993 16:54 | 7 |
Maybe you have corrupted target MIRs. You may want to try renaming
(or just blowing away) the target MIR data files. I believe the
software will re-create them when you assign a new target. I seem to
remember running into this before.
Dave
| |||||
| 5306.2 | Maybe your notification was not enabled successfully | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Tue Aug 10 1993 13:43 | 7 |
I have this problem every time I try to enable a notify request on a
node with insufficient resources, or one that is not fully registered.
Look at "Notify requests..." and watch the status of the requests
during the enabling process. Check each one that reports the problem
you mentioned to see that all is in order.
-Dan
| |||||