| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5138.1 | Data Collector 101 - part deux... | TOOK::MCPHERSON | Dead or Canadian? | Thu Jun 03 1993 00:31 | 53 |
| Boy, this is the day for Data Collector AM questions, I guess... ;^)
Merlin, you're the 2nd person today that swears they read the docs and it's not
working... I'm starting to smell some bogus examples in the docs... I won't be
in tomorrow, but maybe someone else will check them out in the meantime...
Anyway..
>First, on my target MCC system, it initially showed that the Collector was
>not registered. Is this normal, or is there some reason that the collector
>did not get registered at installation time?
A collector is a class of 'registerable' objects, just like a NODE4 or SNMP
object. You register a collector to act as the recipient of a data collector
event. For example:
MCC> REGISTER COLLECTOR Security-Problems
MCC> REGISTER COLLECTOR Backup-Problems
MCC> REGISTER COLLECTOR Trouble-Tickets
>After registering the Collector and starting the DECnet event sink as
>desribed in Section 6 of the Alarms/Notifications manual everything appears
>to be set up correctly on the MCC system.
I assume this means you did a
MCC> ENABLE MCC 0 COLLECTION SINK DECNENT
from an account with sufficient DEFAULT privileges (i.e. the SYSTEM account).
It's not sufficicent to enable the sinks from an account with SETPRV -- they
have to be *default* priv's in order to startup the sink process & declare the
DECnet object, etc.
>However, when I customize and try to run one of the sample Collector scripts
>I get a device timeout error message. Specifically the message is:
>
> %SYSTEM-F-TIMEOUT, device timeout
>
>I've tried running the script on the SAME system that I have MCC running on,
>and get the same results.
Did you create a NOTIFY request for the collector(s) in question?
Ex:
MCC> notify domain FOO entity = (Collector *), event = (Any Event)
Once that's done, just try sending an event using the mcc_evc_send.exe program
$ mcc_evc_send :== $sys$mcc_wherever:mcc_evc_send.exe
$ mcc_evc_send MYNODE Security-Events "" "Testing 1-2-3" "This is a test" -
_$ minor decnet
$
Do you get an event then?
Bedtime.
/doiug
|
| 5138.2 | 7th Arg = PROTOCOL | SPANKY::SAWYER | | Thu Jun 03 1993 10:14 | 12 |
| Merlin,
Check to see that you have included the seventh argument with the
SEND EVENT Directive.
With MCC 1.3 you need to include the protocol, either DECNET or UDPIP
as your 7th argument.
This was a change from MCC 1.2 where it just defaulted to DECnet.
Regards,
Rob
|
| 5138.3 | Unexplained Behavior ... | TRIGG::TRIGG::CLAYTON | Merlin Clayton DTN 445-7217 | Thu Jun 03 1993 13:28 | 28 |
| After successfully sending a test event as suggested by Doug in .1 I went
back and looked at the sample procedures and discovered that they did not
include the protocol argument. When I included the protocol argument, the
procedures worked the same as the manual send_event command.
So that much is fixed...However, I'm still seeing unexplained behavior.
When I set up the notification event on my MCC system for a COLLECTOR
DISK-PROBLEMS entity, the notifications that I receive are for a REFERENCE
entity. Don't understand.?!
I have defined and registered the COLLECTOR entity called "DISK-PROBLEMS" on
my MCC system from the ICMP. I have enabled the DECnet event sink. I have
defined an "Occurs" rule for entity COLLECTOR DISK-PROBLEMS for "any event"
from the ICMP.
On the remote system I specify "DISK-PROBLEMS" as the collector on my MCC node
in the CHECK-DISK.COM procedure, and run the procedure. The event gets sent
out from the remote system, but when I receive it on my MCC system, the
DISK-PROBLEMS Collector ICON does not turn colors, the event fires in the
notification window however, as a "REFERENCE" entity called DISK-PROBLEMS.
Any thoughts on this?
Merlin,
|
| 5138.4 | Couple of Suggestions.... | SPANKY::SAWYER | | Thu Jun 03 1993 15:40 | 13 |
| Merlin,
That IS odd because the variable THIS_NODE is what should be turning
color and that is assigned to sys$node or the icon for the remote
node.
Two Suggestions:
1. Make sure that you have the node registered in DECmcc
2. Make sure that you don't have an Event Targeted to that
Reference Icon Under NOtification Services...this might
be why IT is turning color.
Rob
|
| 5138.5 | have you increase timeout? | TOOK::JEAN_LEE | | Fri Jun 04 1993 15:49 | 19 |
|
Reply to .0 too - regarding time out
Hi,
Do you still see "Device time out" message?
If you do, try to increase timeout a little by doing:
$define UDP_TIMEOUT 10 (any number)
The default is 5 seconds. The sender waits for confirmation from
the event receiver. The receiver by now already got the event, so
it is not a problem.
Let me know if increase timeout helps.
Jean
|